Executions

The Executions tab in Pulse gives you a searchable history of every workflow run on your tenant. Use it to confirm a workflow handled a request as expected, investigate failures, or trace the exact data that flowed through each node.

---

​

Open the Executions tab

From the Pulse dashboard, switch from Overview to Executions at the top of the page. The tab shows the most recent runs (up to 100) matching the current filters. Each row represents a single workflow run with the following columns:

---

​

Filter the list

Filters apply together — a run must match every active filter to appear. Filters are debounced, so the table updates a moment after you change a value.

• Workflow — limit to runs of a single workflow. Defaults to all workflows.
• Area — limit to runs whose workflow was assigned to a specific area.
• Stage — limit to runs that came from a Draft, Staging, or Production version.
• Date range — pick a preset (Today, Last 24h, Last 7 days, Last 30 days, All time) or choose Custom range to enter exact From and To timestamps.
• Mail Id — exact-match search by the request identifier. Useful when you have a specific request you want to trace.

If no runs match, the table shows “No executions match the current filters.” — relax a filter to widen the search.

​

Statuses

---

​

Inspect a single run

Click any row to open the execution detail drawer. The drawer shows a read-only copy of the workflow graph as it ran, plus run metadata:

• Status, Stage, Areas — the same values shown in the table.
• Started and Duration — the start timestamp and total elapsed time.
• Mail Id — the full request identifier (not truncated).
• Workflow graph — every node from the version that ran, hydrated with its input, output, and status.

Click any node in the graph to see the exact data it received and produced during that run. This is the fastest way to pinpoint where a workflow diverged from what you expected — for example, a switch node that took an unexpected branch, or an HTTP node that returned an error response.

---

​

When to use Executions

• Verify production behavior — after activating a workflow, watch the Production stage to confirm live requests are handled correctly.
• Debug a reported issue — paste a Mail Id from a support ticket into the Mail Id filter to jump straight to the relevant run.
• Compare runs across stages — filter by Stage to compare how Draft, Staging, and Production versions of the same workflow behaved.
• Audit recent activity — use the date presets to review what ran in the last 24 hours, week, or month.

---

​

What’s next

• Test a workflow before promoting it to Production.
• Versions and stages — understand how Pulse tracks each saved version.