Monitoring workflow runs and versions

Once a workflow is activated, Dalil automatically executes it when the defined trigger occurs. Dalil gives you two levels of visibility: a workspace-wide overview across all workflows, and a per-workflow runs history.

The Workflows Overview

The overview page summarizes automation health across the workspace:

• Run health: how many runs succeeded or failed over time
• Needs attention: workflows that are currently failing
• Failures by cause: what is making runs fail, grouped by error type
• Runs and outcomes: recent executions and their results
• Token consumers: which workflows use the most AI tokens (relevant when using AI Agent steps)

Use this page as your daily health check before digging into an individual workflow.

Workflow Runs

Each run represents a single execution of a workflow. A run moves through these statuses:

• Not started: created but not yet picked up
• Enqueued: waiting to execute
• Running: currently in progress
• Completed: finished successfully
• Failed: stopped with an error

From a workflow's Runs view you can monitor each execution, when it started, how long it took, and which version of the workflow it used. Monitoring runs helps teams confirm that automations are functioning correctly and identify potential issues quickly.

Execution Logs

Each workflow run includes a detailed step-by-step log showing how the automation was processed. For every step, you can inspect:

• The trigger event details
• Which steps executed, and their status
• The input data passed to each step
• The output each step produced (available to later steps as variables)
• Errors or failures encountered

This visibility is essential for debugging automation logic when workflows fail or behave unexpectedly; you can see exactly which step failed and what data it received.

Workflow Versions

Dalil workflows maintain version history so changes can be tracked and managed safely. Every time you activate a workflow, the current draft becomes the new Active version; previous versions are kept in the history.

A workflow and its versions move through these statuses:

• Draft: being edited; never runs
• Active: the version that executes when the trigger fires
• Deactivated: turned off; kept in history
• Archived: an old version superseded by a newer one

With version history you can:

• Review previous versions and see how the automation evolved
• See which version each run used when debugging
• Take an earlier version and use it as your new draft (Override Draft) to roll back a bad change
• Discard draft to abandon unpublished edits and keep the active version as-is

Version control helps teams experiment with improvements while maintaining operational stability: the active version keeps running untouched while you edit the draft.

Notifications

Dalil surfaces workflow events in your notifications:

• Workflow failures: so broken automations are noticed quickly rather than failing silently
• Form input requests: when a workflow reaches a Form step, the assignee is notified that the workflow is waiting for their input

Check the Needs Attention panel on the overview page regularly to keep automations running reliably.