Workflows and parallel runs
Follow each workflow or AI-agent execution, including simultaneous runs.
On this page
What you need
A Workflow or AI-agent monitor and an integration that can report start and completion.
How to do it
- Create the monitor and choose the measurements or events you want to report.
- Create a new run UUID for each execution. Send started, then succeeded, failed or aborted with the same run ID.
- Open the run history to compare outcomes and durations. Add a run alarm if needed.
Good to know
Parallel runs remain separate. Keep event IDs and content unchanged when retrying. Reported duration, exit code and AI costs come from your integration.
Prompts, full logs and customer content are not collected automatically. Send only the short details you want to monitor.
If something goes wrong
A conflict usually means the same run ID has different data. Compare the original report before resending or starting another execution.
Related guides
- Monitor jobs and cron schedules
Track scheduled commands and find failed, late or missing executions.
- n8n metrics and error workflows
Use the n8n examples to send readings and report workflow errors.
- Text events and severity
Report short events with a timestamp and severity instead of uploading full logs.
- Job and workflow run alerts
Get notified about failed, aborted, overlong or missing job and workflow runs.