Troubleshooting

Overview

A workflow is one trigger → a chain of actions wired by edges, run immediately when the event fires. Most problems are one of: it didn’t fire, an action failed and stopped the run, a {{token}} didn’t resolve, or a condition sent the run down the wrong branch. Every run is recorded. Open the workflow’s Runs tab to see the trigger data, each action’s input and output, and any error.

Common issues

Symptom	Likely cause	What to check
Workflow never runs	It’s disabled, or the trigger’s filter didn’t match the event	Confirm the workflow is enabled; check the trigger filter (e.g. Property Updated set to a specific value).
Runs but stops partway	An action failed. The run is marked failed and stops at that step	Open Runs, find the failed action, and read its error.
A `{{token}}` comes through empty or literal	The value isn’t available from that trigger, or the path is wrong	Use the editor’s available-values list for your chosen trigger. A token only resolves to data that trigger actually provides.
A condition took the wrong branch	Edge order or rule logic	The first matching conditional edge wins, review the rules (and / or, operators equals / not-equals / greater / less / contains) and the edge order. The else edge catches whatever didn’t match.
You wanted a wait / delay between steps	Workflows run all at once	A long wait belongs in a Sequence step, not inline in a workflow.
Can’t wire an edge back to an earlier node	Cycle detection. Workflows flow forward	For iteration over time use a Sequence; to iterate a list in place use a Loop action.
A Loop skipped items or stopped early	The loop’s per-item error behavior	Set the loop’s error behavior (stop, warn, or ignore) to match what you want when one item fails.
A Send Email / SMS / Call action did nothing	No connected channel, or the recipient couldn’t be resolved from the trigger record	Confirm a connected channel, and that the trigger provides a recipient (a record with an email / phone).
Need multiple starting conditions	One trigger per workflow	Create separate workflows pointing at the same actions, or use a Sequence.

When reporting an issue, include the request id shown in the error toast. It links the in-app error to the server logs.

Getting started

Workflows

Sequences

Jobs

Overview

Common issues

​Overview

​Common issues

​Related

Overview

Common issues

Related