Monitor and repair workflow runs

A workflow definition explains what should happen. A workflow run shows what happened this time.

Open run history#

Open Workflows, select a workflow, and review its recent runs. A run shows how it started, its state, and its step results.

Runs can be manual or scheduled. Common states include queued, running, waiting for approval, completed, failed, and canceled.

Inspect every step#

Open the run and read the steps in order. A top-level state alone may not explain the problem.

A step can show:

• Completed output
• Work in progress
• A required approval
• A cancellation
• An error message
• A step that has not started

Confirm that the output of one step is suitable input for the next.

Resolve an approval gate#

When the workflow is waiting, read the approval banner. Check its title, action, content, target, and any expiry date.

• Choose Approve to let the guarded step continue.
• Choose Reject to stop that proposed action.
• Add a note that explains a rejection or important condition.

After approval, refresh or reopen the run and confirm that later steps complete. Approval does not guarantee that a connector accepts the action.

Cancel an active run#

Choose Cancel when the run is still in progress and should not continue. The control can apply to one or more active runs for the workflow.

Cancellation stops remaining work where possible. It does not undo an external action that already finished.

Repair a failed run#

1. Open the first failed step.
2. Read its exact error.
3. Check the department state and plan limits.
4. Check required connectors and permissions.
5. Correct missing or invalid input.
6. Confirm no earlier external action must be reversed.
7. Use Run now for one controlled retry.

Do not repeatedly retry a permission or credential error. Fix the connection first.

Avoid duplicate results#

Before retrying a publishing, messaging, record-creation, or calendar step, check the external destination. The earlier step may have succeeded even if the final status was not recorded.

If a workflow failed after some steps completed, note those completed outputs in the retry request or repair plan.

Escalate with useful details#

Record the workflow name, run time and time zone, trigger type, failed step, visible error, connector, and expected result. Never include secret credentials in the report.