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
- In the left menu, select
Execution History. - Select the
PersonalorTeamtab. - Find the workflow execution record you want to check in the list.

Checking Execution Results
The execution history list shows the status, workflow name, run type, executor, start time, and duration.
| Item | Description |
|---|---|
Status | Indicates whether the run succeeded or failed. |
Workflow | The name of the workflow that was run. |
Type | Shows how the run was started, such as Manual, Scheduled run, External request, Event, Test, or Step test. |
Executor | The user who started the run. |
Start Time | The time the workflow was run. |
Duration | The 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.
- Select the
PersonalorTeamtab. - In
Search run history, enter a workflow name, run ID, or the user who ran it. - If needed, narrow the list with
Run statusandRun type. - Select the record to check
Run summaryandResults by step.
Search applies only to the loaded runs.

Checking Status
| Status | Description |
|---|---|
Success | The workflow run completed. |
Failed | An error occurred during the run. |
Running | A run that has not finished yet. Records started via Test Start Condition or Test Step show Test or Step Test under Type. |
Needs review | The run result could not be confirmed. |
When Reviewing a Failed Run
- Find a record with
Statusset toFailed. - Check the name of the workflow that ran and its start time.
- Check any recently modified triggers, block settings, file paths, or mail conditions.
- 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 secondmay be a test run or a very short-lived execution.