LouiseA
LouiseA2mo ago

Created 2 API blocks but 2nd one is not triggering

Hello, I'm trying to build a Dynamic Carousel; I created 2 API blocks for testing purposes. When I run the entire workflow the 2nd API block is not being triggered. Here are screenshots of: 1. The workflow 2. Ist and 2nd API blocks 3. Set block
No description
No description
No description
No description
2 Replies
Tico | Voiceflow Assistant
Here are the quickest things to check when an API #2 never runs: 1. Verify the canvas connection • The API step only moves forward through the port you connect. – Success = “Default” port. – Error (4xx / 5xx, timeout, bad JSON, etc.) = “Failure” port (only visible if you toggled it on). If the Default/Failure port isn’t linked to the second API block, the execution stops there. 2. Confirm the first call is succeeding • In the API-1 editor press Send Request. You should see “Success” and a 2xx status. • If you get an error, the block will drop to the Failure path at runtime – and API-2 will never be reached unless that path is wired up. 3. Check for hidden “wait” steps • Steps like Speak + Listen, Choice, or a Custom Action with “Stop on action” will pause the flow until the user/client responds. Make sure nothing between API-1 and API-2 is waiting for input. 4. Validate variable mappings • If you’re capturing a value from API-1 and then inserting it into API-2’s endpoint/body, make sure the variable actually contains data (test in the Debugger or add a temporary Speak block to print it). 5. Use the Failure path for safety • When you enable the Failure port and connect it back into the flow (e.g. a Text step that says “API 1 failed” ➜ then route to API-2 or an exit), you’ll know immediately if the first call is breaking. Typical fix order
API-1 (test → succeeds) ──Default──▶ API-2
└──Failure──▶ <error handling>
API-1 (test → succeeds) ──Default──▶ API-2
└──Failure──▶ <error handling>
Once API-1 returns “Success” and that Default line is connected, API-2 will fire automatically. Docs reference – API step overview, paths, testing & troubleshooting: https://docs.voiceflow.com Try the steps above; nine times out of ten the issue is an un-connected port or an error in the first request.
LouiseA
LouiseAOP2mo ago
This issue has been resolved. Thank you.

Did you find this page helpful?