Troubleshoot automation and campaigns
Resolve paused, waiting, failed, repeated, or partially completed automated work.
- For
- Workspace users and support owners
- Owner
- Automation product
- Outcome
- Identify the failure state, recover without duplicate work, or contact support with safe evidence.
- Last verified
- 2026-08-30
- Next review
- 2026-11-28
- Status
- supported
Start from the visible symptom, the affected workspace, and the approximate time. Confirm the current state before repeating an action.
What you can see
- A run is waiting, paused, failed, or appears stuck.
- Only part of the audience or journey completed.
- A provider side effect completed but the Sakhaa run state is uncertain.
Check the current state
- Confirm the exact version, audience, owner, start condition, and stop condition.
- Inspect run evidence and provider state for the affected step.
- Confirm whether a wait, approval, credit, connection, or provider limit explains the state.
- Identify completed side effects before retry, resume, or cancellation.
Recover safely
- Pause the affected path while the failure is understood.
- Resume or retry only from the supported control and only after completed work is known.
- Keep partial completion visible and preserve the original run evidence.
- Use a bounded synthetic audience to prove the repaired path.
Do not clone or relaunch a campaign when the original provider side effects are uncertain.
Contact support
Send the workspace, page, approximate time, safe error code, expected result, actual result, and checks already completed.
- State whether you repeated the action and whether it can create an external side effect.
- Do not send passwords, tokens, API secrets, webhook secrets, message content, or unnecessary customer data.