Troubleshoot an automation
Start with the symptom and the version involved. Draft checks and previews describe editor work; Runs describes executions of published versions.
Automations is in Early access. Your workspace permissions determine which actions you can perform.
Automations is missing from the dashboard
Confirm you selected the intended workspace and are a member with permission to view Automations. Ask a workspace administrator to check your access if Automations is missing.
Editing controls are missing
Automations read access lets you view templates and workflows. Creating drafts and publishing require Automations write access. If Use template or Publish is unavailable, ask your workspace administrator for write access.
No run appears
- Confirm the automation has a published version and is active, rather than paused or archived.
- Inspect the published trigger. Unsaved or unpublished edits do not affect incoming events.
- For a Bird event, confirm the receiving channel got the message and test the trigger filter with representative data.
- For an application event, compare its name and required fields with the published trigger and check the source application's connection.
- For a schedule, inspect its next occurrence, timezone, and missed-tick behavior.
- Check whether an active run caused the new start to be skipped.
A filter miss or overlap skip creates no run. Acceptance of an application event means it was queued; inspect Runs for subsequent execution progress.
Publication is blocked
- Finish open field edits and save the draft.
- Open Checks and follow each blocking finding to its step or field.
- Check required inputs, output connections, and references to missing or future steps.
- Remove cycles and repair invalid nodes even when they are disconnected from the main path.
- Review permissions and any requested application-event contract confirmation.
If the draft changed in another editor, reload and compare the current work before trying again. An earlier check result may be out of date.
Preview stops at an action or wait
Inspect the prepared input. If preview reports an incomplete path, supply a sample outcome using Set sample result, then preview again.
Preview cannot fetch a contact or wait for a real receipt to fill a missing sample. If the sample itself is invalid, repair its node, output path, or fields to match the current configuration.
A field is missing or an expression fails
- Select the consuming step and inspect the source mapping.
- Confirm the source step occurs earlier on the chosen path.
- Check whether the field is absent, null, empty, or a different type in the sample or recorded run.
- Add a condition or explicit fallback where appropriate.
An output on an untaken branch is unavailable. A successful contact search with no results also needs an explicit empty-result path.
A run remains waiting
Inspect the delay deadline or wait configuration. Confirm the expected event type, the watched send step or business key, and any filter.
For an application-event wait, the follow-up event must address the key of an existing run. For a receipt wait, the receipt must belong to the configured action in that run. Waiting is an expected state until a match, timeout, cancellation, or run deadline resolves it.
A run succeeds but no message arrives
Inspect the run's path first: a branch may intentionally finish without sending. If a send ran successfully, inspect the message's channel status. Acceptance can be followed by a delivery failure.
Use a supported delivery wait for follow-up decisions. A timeout alone is not proof of non-delivery, so check before sending a replacement message.
A run fails after a partial change
Inspect the failed step and the earlier successful steps. A contact batch can contain successful and failed entries. Cancellation or a later failure does not roll back an accepted message or contact change.
Correct the cause before starting a new run. Review which actions would happen again to avoid repeating work that already succeeded.
Next steps
相关资源
继续查阅此主题的文档、指南和示例。资源为英文。