Keep track of every workflow run
Keep track of your workflows
Track results, runtimes and failures. Unique run IDs keep parallel workflows separate.
Free to use · view quotasEach run has its own ID
run-104Started
- Duration
- —
run-105Started
- Duration
- —
run-103Succeeded
- Duration
- 38 s
run-102Failed
- Duration
- 12 s
- Exit code
- 1
Each run has its own ID
run-103Succeeded
- Duration
- 38 s
Each run has its own ID
run-102Failed
- Duration
- 12 s
- Exit code
- 1
Each run has its own ID
No matching runs in this example.
What you can monitor
Understand every workflow run
Give every run its own ID.
Separate executions
Execution status
Run times
Details for troubleshooting
Understand your data
Keep parallel executions organized
Use the same run ID for start and result. Send status and useful diagnostic details; keep prompts, customer content and full logs out of monitoring data.
Each run has its own ID
run-104Started
- Duration
- —
run-105Started
- Duration
- —
run-103Succeeded
- Duration
- 38 s
run-102Failed
- Duration
- 12 s
- Exit code
- 1
Each run has its own ID
run-103Succeeded
- Duration
- 38 s
Each run has its own ID
run-102Failed
- Duration
- 12 s
- Exit code
- 1
Each run has its own ID
No matching runs in this example.
Your first steps
Connect your workflow
Connect your source in three steps.
- 01
Create a workflow monitor
Choose a workflow monitor in the workspace that owns your automation.
- 02
Report each run separately
Use the same run ID when reporting the start and result through your integration.
- 03
Add an alert rule
Configure the relevant alert and test it with an example execution.
Good to know
Frequently asked questions
Answers and setup guides.
Can workflows run concurrently?
Do I need to send full logs or prompts?
How are missing runtimes shown?
Your next step
Give your next workflow run an identity
Create a workflow monitor and report start and result.