Retry, pause, and roll back automation work

Choose recovery by affected scope

Lifecycle recovery controls are available to Owners and Admins. Members can inspect evidence and, where the UI permits an approved workflow release, follow the approval boundary; they should escalate lifecycle changes to an accountable administrator.

Pause before diagnosis

From the automation directory, use the workflow switch or menu to Pause automation. Confirm the directory shows Paused. Existing waiting work is separate; inspect Runs to decide whether individual pending items must be cancelled or rescheduled.

Retry one run

1. Open the workflow's Runs and expand the failed or partial run.
2. Check the published version, completed steps, and receipts.
3. Select the retry action. WRKZY first offers a retry simulation.
4. Read which steps would execute, skip, or reuse.
5. Only after the simulation passes, choose Retry live and confirm Retry original version.
6. Watch the new run to completion.

A live retry uses the original published version and saved input. Completed effects are reused from receipts; uncertain effects remain blocked to prevent duplicates.

Recover waiting work

In Runs, locate the waiting item. Cancel waiting work prevents only that run from continuing. Choose a new resume time changes only that item; it continues from the same published version and saved step. Record why the exception was made.

Roll back a workflow version

1. Pause the workflow.
2. From the automation card menu, open Version history.
3. Compare version number, timestamp, actor, trigger, and description with the last known-good release.
4. Select the version and confirm Make live.
5. WRKZY publishes that snapshot as a new version and keeps the current draft.
6. Test the new live version, then turn the workflow on and monitor the first runs.

Open full size

Archive and restore

Archiving stops the automation and cancels waiting runs; versions and run history remain. Restoring returns it as Paused, which is intentional. Revalidate, test, and explicitly turn it on.

When not to retry

Do not retry when a receipt is uncertain, the customer already received the message, the CRM change was manually completed, the underlying provider is still unhealthy, or the saved input is no longer valid. Resolve or document the business outcome instead.

Escalation evidence

Preserve the workflow and run IDs, original and recovery version numbers, retry simulation result, receipt states, waiting-item ID if applicable, approximate times, and redacted error. Never rotate or disclose credentials as part of an unverified retry.