PeertopeerC
PeertopeerC7h ago

Custom action WITH STOP ON ACTION TURNED ON - does not receive Success path on time and ends chat

Here is a mystery for you!. Custom action with an extension register with a web site and a Success path that sould always be triggered by the web site with an interaction action ignores the STOP ON ACTION being turned on and ends the conversation while waiting for an Interaction with a type Success
2 Replies
Tico | Voiceflow Assistant
Here’s what normally has to happen for a “Stop on Action ✓” Custom Action to pause the flow and wait for your website to respond with the ​success​ event: 1. In the Voiceflow project
• Custom Action block has “Stop on action” enabled.
• You added an outgoing path called success (exact-case match). 2. From the client (your extension / website)
• The first interact request that reaches this Custom Action must include
"config": { "stopTypes": ["Your Custom Action Name"] }

"config": { "stopTypes": ["Your Custom Action Name"] }


Otherwise the Dialog-Manager keeps executing and will hit the End step, even though “Stop on action” is checked in Creator. • The Dialog-Manager response you get back will end with a trace:
{ "type": "Your Custom Action Name", "paths": [{ "event": { "type": "success" } }], ... }

{ "type": "Your Custom Action Name", "paths": [{ "event": { "type": "success" } }], ... }

As soon as you receive that trace you should send a second interact call:
{ "action": { "type": "success" } }

{ "action": { "type": "success" } }

DM will then follow the success path and continue the conversation. Most “flow suddenly ends” issues come from one of these: • stopTypes not supplied in the initial interact call – DM never pauses.
• Path name mismatch (e.g. “Success” in the block but you send "success" or vice-versa; path names are case-sensitive).
• No outgoing path on index 0, so DM falls through to the default path that ends the chat. Quick checklist ---------------
✅ Add the success path to the Custom Action block.
✅ Use exactly the same string in the second interact request’s action.type.
✅ In every request that should pause at that block, pass
&nbsp;&nbsp;config.stopTypes: ["<Custom Action Name>"]. Docs for reference: https://docs.voiceflow.com/docs/custom-action-step
PeertopeerC
PeertopeerCOP6h ago
this does not work alos why instruct it to wait from the web page with an interact if in voiceflow I already instructed the custome action to wait for the response of the web site

Did you find this page helpful?