Troubleshooting
What workflow warnings mean and how to fix runs that take the wrong path or never start.
| What you see | What it means | Fix |
|---|---|---|
| Only one trigger node is allowed | The workflow has two triggers. | Delete one. To react to two kinds of events, build two workflows. |
| Connect this node to the trigger | The node isn't linked to the chain, so it never runs. | Drag a connection to it from an earlier node. |
| Set delay to more than 10 seconds | Delay nodes need more than 10 seconds. | Enter a longer delay in seconds: 120 is 2 minutes, 7200 is 2 hours. |
| Template banner about integrations | Red nodes need your own account or campaign. | Open each red node, choose your integration or campaign, then save. |
| Condition always goes to FALSE | The field is empty, misspelled, or has extra braces. | Open the run, click the condition, and check the compared value in Input. Re-insert the field with @. |
| Switch always goes to Else | Case text doesn't match exactly (spelling, capitals, spaces). | Match the exact words, or tell the AI to answer only with those words. |
| Call goes to REJECTED | The number was invalid, busy, or didn't answer. | Use international format with the country code. Add a retry path. |
| Live link does nothing | The workflow isn't published, the Production switch is off, or Active is off. | Publish, switch on the trigger's live link, and check Active in the published view. |
| Edits aren't live | You saved the draft but didn't publish. | Click Publish. |
| Wait for Time didn't wait | The time was in the past or in the wrong format. | Use YYYY-MM-DD HH:MM:SS and check the timezone. |
Example: from new lead to follow-up
An end-to-end journey with two workflows and a Dynamic Bulk Call campaign. Queue every new lead, let the campaign call them, then act on how each call went.
Web call protocol
The WebSocket protocol behind web call sessions, for iOS, Android, Flutter, kiosks, and any platform without an official SDK.
