Troubleshooting workflows
Start with one concrete event or run. Identify the workflow version, expected input and time, then compare the expected path with the observed steps. A draft preview and a published run may use different definitions or record values.
No run appearedโ
Check that the workflow is published and enabled, the trigger uses the correct object, and the event happened after activation. For Record updated, check whether at least one selected field actually changed. Existing records are not processed merely by publishing. Workflow-originated record writes do not trigger further workflows.
For a manual start, verify that the publication uses Manual record and that you can access the selected record. For a recurring trigger, inspect schedule status and timing rules: an earlier open run, lateness, an invalid date or daylight-saving ambiguity can cause a skip.
The run exists, but the result is unexpectedโ
| Symptom | What to check and do |
|---|---|
| Publication is blocked | Open each validation issue. Complete required settings, connect every outcome, correct mappings and complete Script/Agent configuration. |
| A step was skipped | Check the selected If/Else or question path. Unselected branches are skipped; End finishes the selected path successfully. |
| A source field is unavailable | Check its type and whether its step precedes the consumer on every path. A default cannot repair an unselected branch. |
| The run is waiting | Inspect the Wait deadline or question Task. Answer through the interaction controls; ordinary Task completion cannot answer a question. |
| A record step failed | Check selected fields, required values, choice identities, related-record access and whether the object schema changed after publication. |
| A Script failed | Read its diagnostics/logs and resolved input. Check output validation and resource limits. Inspect committed effects before starting another run. |
| An Agent failed | Check required inputs, model/capability availability, output validity and remaining budgets. Usage can exist without accepted output. |
| A completed run has missing steps | Check history freshness and refresh. Synchronization may lag; do not infer that no effect occurred. |
What preview can tell youโ
Preview helps resolve values, conditions, paths and timing without changing data. It does not execute Scripts, Agents or record actions, answer questions, or simulate schedule overlap and outages. It also cannot prove a changed-field trigger match without a real event. An unknown preview output is not itself an execution failure.
Recover with the actual results in viewโ
Pausing prevents new starts; cancelling targets an existing run. Neither undoes committed effects. Do not repeatedly start new manual runs to compensate for delayed history. A new start can duplicate business work.
If the issue persists, contact support with the workflow/run identifiers, version, approximate time and timezone, affected step, visible error and expected outcome. Include the relevant configuration or a screenshot without unnecessary private data. Do not include credentials or API keys.
Agent record access failsโ
An Agent's saved record scope must permit the object and selected fields it reads. An access denial, missing record, or invalid tool input stops the step without retrying the identical request until its time limit. Inspect the failed step, correct its input or the Agent's permitted record scope, publish the correction, and start a new run. Temporary infrastructure failures retain their retry behavior. A published correction does not change a run already in progress.