Monitoring workflow executions
View run history, check step-by-step results, and troubleshoot failed runs.
After you've set up a workflow, you need to know if it's running correctly. The execution history gives you full visibility into every run.
View execution history
- Go to Setup > Configuration > Workflows.
- Click on the workflow you want to inspect.
- Open the Execution History tab.
You'll see a list of every time the workflow fired, with:
- Timestamp - when it ran
- Status - completed, failed, running, cancelled, queued, or digest_pending
- Duration - how long the execution took
- Trigger event - what caused it to fire
Inspect step-by-step details
Click any execution to expand the step-by-step breakdown. For each step, you can see:
- Input data - what data was available to the step
- Output data - what the step produced (e.g., the message sent, the action created)
- Status - whether the step succeeded or failed
- Error message - if it failed, what went wrong
Troubleshoot failed runs
Common reasons workflows fail:
Connection issues
If a Slack, Teams, or webhook step fails, the connection may be misconfigured or the external service may be down. Check:
- Is the connection still active in Setup > Connectors?
- Is the webhook URL still valid?
- Has the OAuth token expired? (Try re-authenticating the connection)
Template variable errors
If a message template references a variable that doesn't exist in the trigger data, the step may fail or send an empty value. Double-check your template variables match the available trigger data.
Rate limit reached
If the workflow is being rate-limited, executions will show as "queued" and run once capacity is available.
Workflow metrics
On the workflow list page, you can see at a glance:
- Trigger count - total number of times the workflow has fired
- Last triggered - when it last ran
- Enabled/disabled status
Next steps
- Make sure your connections are healthy if messaging steps fail
- Review trigger types to adjust when your workflow fires