Monitoring and history
Every run of an automation is recorded. You can watch a run unfold live and review past runs step by step, with the logs and output each step produced.
The dashboard
The Dashboard is the landing page for the automation area. It summarizes recent activity with metric cards—Active Automations, Automations Triggered, Avg. Execution Time, Success Rate, and Cost—and two charts: an Automation Activity Trend over time and an Execution Health breakdown of successes and failures. Use the period selector (Today, Past 7 Days, Past 30 Days, Past 90 Days) to change the window.
The automations list
The Automations page shows each automation's recent run history at a glance—its run count, when it last started and completed, how long the last run took, and its last status. The Runs link opens that automation's full run history; the Last Execution link opens the most recent run.
Select Show Archived to include archived automations in the list. An archived automation's row is muted and marked with an amber Archived pill beside its name, so it reads as inactive at a glance without changing what its Status column shows.
Recent activity in the editor
Opening an automation in the flow editor shows a live activity strip in the side panel: a last-run badge with a status icon, and a strip of beads—one per recent run, colored by outcome (a running one pulses blue)—with a View all runs link to the full history below. New runs appear and recolor in place as they start and finish, without reloading the page.
Click a bead or the last-run badge to open that run's Workflow view. Hovering either shows a tooltip with the run's number, status, mode (Live or Dry Run), start and end time, duration, and cost.
The runs list
The Runs link from an automation opens its full run history—every run, newest first, filterable by status and archived state. Started At and Completed At show a relative label by default ("15 hours ago"); toggle Full Timestamps in the filter bar to also show the exact date and time alongside it. The toggle is remembered for you and applies across pagination.
Run notifications
Subscribe to be told when an automation's runs finish, from your profile's notification settings, delivered through Brightspot's normal notification channels (email, Slack, the in-CMS bell). By default you're notified only on failure; opt in to also hear about successful runs. Scope the subscription to specific automations, or leave it open to every automation on the site. Each notification links straight to the run, and a failure notification names which step or steps failed.
Viewing a run
A run opens in one of two views, switchable with the Workflow and Steps tabs:
- Workflow shows the flow on a read-only canvas, with each node's status overlaid on its card. While a run is live, the view updates in place as steps progress, so you can watch the flow execute.
- Steps shows a table of every step, with its status, timing, and links to that step's logs and output.
A running execution can be cancelled with the Stop button on the execution detail pages. The run is marked cancelled the moment you click, no matter how large it is, and nothing further in it begins. Steps that hadn't started then settle to Cancelled over the next few seconds, so you may briefly see a cancelled run with some steps still listed as pending.
A step that was already mid-way through its work is allowed to finish rather than being cut off. This is deliberate: if that step had already changed something on the target system, cutting it off would record it as failed while the change stayed in place, and the run history would understate what the automation did. Letting it finish means the history matches reality. So a stopped run can show one last step completing a moment after you press Stop.
Statuses
As a run progresses, each step moves through statuses shown on its card or row:
- Running—the step is executing.
- Waiting / Awaiting Input—the step is paused, for a timer, an external event, or human input.
- Done—the step completed successfully.
- Error—the step failed.
- Cancelled—the step was stopped.
- Skipped—the flow did not route to the step.
Logs and output
From the Steps view you can open a step's:
- Logs—a timeline of entries, filterable by level (System, Debug, Info, Warn, Error), including status transitions and any messages the step produced.
- Output—the payload the step produced, shown as formatted data, or the error message if it failed.
Secret values are redacted from both logs and output. When a loop runs, logs and output are recorded per iteration so you can inspect any single pass.