Workflows

Runs and history

Inspect every execution of a workflow to confirm it is doing what you expect.

Every time a workflow's trigger fires, Kudoso starts a run. The run history is your record of exactly what the automation did, and when.

What a run records#

Open a workflow and look at its runs. Each run shows:

  • When it started, and what triggered it.
  • Which steps executed, in order.
  • The outcome of each step: completed, waiting, or failed.
  • Where the run currently is, if it is still in progress (for example, paused on a wait step).

Why run history matters#

Automation you cannot see is automation you cannot trust. The run history lets you:

  • Confirm a workflow is firing when it should.
  • Debug a flow that is not behaving, by seeing which step it stopped at.
  • Verify that emails actually went out.

Runs in progress#

A workflow with a wait step will have runs that sit in progress for a while. That is expected: the run is paused, counting down, and will resume on its own when the wait elapses. You do not need to do anything.

Note

A run reflects the workflow as it was when the run started. If you edit a workflow, the change applies to new runs, not ones already in flight.

When a step fails#

If a step fails, for example an email could not be sent, the run records it. Check the email settings if sends are failing, since most email step failures trace back to a sending configuration problem.

Next steps#