Skip to content

Checking Execution History

Execution History lets you check when a workflow ran and whether it succeeded, failed, or was a test run.


Opening Execution History

  1. In the left menu, select Execution History.
  2. Select the Personal or Team tab.
  3. Find the workflow execution record you want to check in the list.

Workflow execution history

Checking Execution Results

The execution history list shows the status, workflow name, run type, executor, start time, and duration.

ItemDescription
StatusIndicates whether the run succeeded or failed.
WorkflowThe name of the workflow that was run.
TypeShows how the run was started, such as Manual, Scheduled run, External request, Event, Test, or Step test.
ExecutorThe user who started the run.
Start TimeThe time the workflow was run.
DurationThe time it took for the run to complete.

Finding an Execution Record

When there are many execution records, use search and filters to find the one you want.

  1. Select the Personal or Team tab.
  2. In Search run history, enter a workflow name, run ID, or the user who ran it.
  3. If needed, narrow the list with Run status and Run type.
  4. Select the record to check Run summary and Results by step.

Search applies only to the loaded runs.

Workflow execution history list

Checking Status

StatusDescription
SuccessThe workflow run completed.
FailedAn error occurred during the run.
RunningA run that has not finished yet. Records started via Test Start Condition or Test Step show Test or Step Test under Type.
Needs reviewThe run result could not be confirmed.

When Reviewing a Failed Run

  1. Find a record with Status set to Failed.
  2. Check the name of the workflow that ran and its start time.
  3. Check any recently modified triggers, block settings, file paths, or mail conditions.
  4. If needed, re-test each step in the workflow's editing screen.

Good to Know

  • Execution History can show not only actual runs but also test runs.
  • What's visible in a team workflow's execution history may vary depending on team permissions.
  • A record showing a duration of Less than 1 second may be a test run or a very short-lived execution.