Default keeps a record of every workflow run, whether a form submission, a CRM change, or a
manual test started it. Run logs show the path the run took, what each node did, and the full
detail behind any warning or error.
In Workflows, select the workflow you want to inspect. Then choose its Logs tab, next
to Graph.
The runs list
The Logs tab opens on a list of every run of that workflow, most recent first.
Columns
Each row shows:
- Version: the published version of the workflow that ran, for example
v3. If that
version is the one deployed now, the row also carries a badge. The badge reads Live
when the workflow is on, and Paused when it is off.
- Record: the person or company the run is about. The name comes first, for example
Jane Doe, with the email or company domain underneath it, for example jane@acme.com.
- Trigger: what started the run, with an icon for the trigger type.
- Status: one of Success, Failed, Running, Suspended, or Pending.
- Timestamp: when the run started.
The icon next to the record depends on what triggered the run. A form submission shows a
contact icon, and a CRM record trigger shows a company icon.
Otherwise the icon is the record’s logo, or its initials if Default finds no logo. If Default
cannot resolve a specific record for a run, this column shows a dash.
A run that finished but logged at least one error along the way shows Errors instead of
Success. A run you started manually to test the workflow also carries a Test badge.
Search and filter runs
Two tools narrow this list: search and filters. Both ask the server for matching runs, so
they work across every page.
Type into the search box, which shows the placeholder Search record, email, or status….
The search matches the record’s name, the contact’s email, and the run’s status.
For example, type @acme.com to find every run for one company’s contacts. The page size and
pagination controls stay available while you search.
Select the Filter button to add a filter. A filter also asks the server for only the
matching runs:
- Status: choose any of Success, Failed, Running, Suspended, or Pending. For example,
choose Failed and Suspended together to see every run that needs attention.
- Email: matches contacts whose email contains the text you enter, for example
@acme.com
to see every run for one company’s contacts.
- Record: matches the same company or person label shown in the Record column, for example
Acme to find every run touching Acme Corp.
- Date: is between two dates, on or after a date, on or before a date, or in the last X
days, for example the last 7 days.
You can add more than one filter. Choose whether every condition must match or only one of
them.
Use Clear all to clear every filter at once.
If nothing matches your search, the list shows No runs match your search. This message
also wins when you use search and filters together.
If filters alone match nothing, the list shows No runs match your filters. If the workflow
has not run yet at all, it shows No workflow runs yet.
Move through pages
At the bottom of the list, a page-size selector lets you show 20, 50, or 100 runs at a time.
Next to it, a count reads “Showing X-Y of N”.
Use the previous and next arrows to move one page at a time. To jump straight to a page, type
its number into the Page field.
Open a run
Select any row to open that run in detail. The view splits in two: the workflow’s canvas on the
left, the run’s details on the right.
The run canvas
The left side is a read-only copy of the exact version of the workflow that ran. Default marks
the trigger that fired and the path the run took through the workflow’s branches.
Any node the run logged a warning or error against carries a small count badge, for example
2 errors or 1 warning. The badge is red for an error and amber for a warning.
Select any node on the canvas to open its configuration exactly as it was at the time of the
run.
The run details panel
The right side opens with a breadcrumb reading Logs. Select it to go back to the runs
list.
You return to the exact page and filters you left.
Run summary and sharing
Below the breadcrumb, a summary card shows who or what the run is about. Its Share Log
button copies a link straight to this run to your clipboard.
If the run came from a scheduling trigger with a recording available, a
View Scheduling Replay button appears alongside it.
Expand Trigger Details to see the trigger itself. When available, a Triggered at
timestamp shows exactly when it fired.
For a CRM record trigger, this card also lists the provider, the object type, and the record
ID involved. A form submission or an incoming webhook does not carry those extra rows here.
Instead, its data shows up further down, under that node’s Show data.
Run timeline
Below the trigger card, Run Details lists every node the run went through, in order. A
Search box filters that list down to nodes that match a name or message.
A node that logged a warning or error carries a count badge, for example 2 errors, and shows
the time it ran. Hover the time to see the exact duration.
Show data
Expand Show data under a node to see the exact values Default read or wrote. The values
appear as a Field / Value table.
Select any row to copy that field name or value. You can also select the clipboard icon that
appears when you hover a row.
Large objects and lists collapse into a compact preview instead of one long line of text.
Expand the preview into a tree and drill in.
For the trigger node at the top of the timeline, Show data shows only what actually fired
the run. An incoming webhook shows just the body it received.
A form submission lists each submitted field as its own row. It leaves out any UTM parameters
that were left blank.
Branch and condition nodes
A branching node in your workflow logs which branch it took and why. The summary names the
branch and states whether its conditions passed.
If no branch matched, the summary shows that the workflow fell through to its
Else branch selected path.
Expand the node to see the full condition breakdown underneath. It lists every condition the
node checked, the value found in this run, and a TRUE or FALSE badge on each one.
The breakdown also calls out AND/OR groupings, so you can see exactly why the run went the way
it did.
Template variable errors
A node can fail because it needed a value from an earlier node and that value was missing. The
error tells you, in plain language, what was missing and where it should have come from.
For example, a “Create Contact” node could not run because it needed a company name from an
earlier enrichment node. That field had no value in this run.
Expand Show available fields underneath to see what values were available to that node at
the time.
Access
If a workflow has not been shared with you, opening its logs shows Access required instead.
Ask an admin or the workflow’s owner for access. 
