Troubleshooting

The app can’t start a chat

• Is the chat key right, and not revoked? A revoked key can’t start a chat. Issue a new one in Chat keys.
• Is a version of the flow published, and is the flow not archived?
• Does the app open the flow by its exact key?

The flow talks but never changes anything

A step that changes data needs a signed-in user. Pass userToken (and refreshUserToken) to the SDK; see the SDK guide. A token refused outright makes the chat ask the user to sign in again.

A flow won’t save or publish

It names something that doesn’t exist: an operation no connector has, a step id, or a slot. The editor counts what’s left to fix. A deleted connector breaks every flow that still calls it.

A call fails

• Its connector’s key isn’t set: set its value in Settings → Keys.
• The answer was too large for the connector’s cap, or the call took longer than its timeout.
• Open the conversation in Transcripts: it lists every request the conversation made, in order.

Test chat didn’t change my data

That’s on purpose. In a test chat, calls that change data are dry runs, shown with the request they would have made.

Messages arrive late in the app

The chat streams new turns, and falls back to polling when the stream is refused or keeps dropping. Each turn shows once, whichever way it arrives.