merchaint · help
Contact supportOpen Merchaint

See what your workflows did

Workspace admin3 min readUpdated 3 Sep 2026
In this article

Automation you cannot inspect is automation you cannot trust. This is where you inspect it.

  • A walkthrough video, then how to follow one run end to end
  • The three tabs on a run, and which one is for you
  • Why an empty page usually means the trigger is not firing
  • Why the timeline calls your steps something else

01 · Video

Feature walkthrough

Video · following one run · 2:30

02 · Why

Why do we have this?

Automation you cannot inspect is automation you cannot trust. When someone asks "why did this invoice get flagged?", this page answers it.

03 · Use cases

Use case 1
Something was flagged and nobody knows why

Find the record, open the run, read the steps.

Use case 2
A workflow does not seem to be doing anything

If there are no runs at all, the trigger is not firing — usually a condition that is too narrow, or the workflow is not Active.

Use case 3
Checking a change you just made

Edit a record, then refresh this page.

04 · How

Follow a run

  1. Open the workflow and press Logs.
  2. Use Status and Triggered by to narrow the list.
  3. Switch between Grouped (by record) and All runs (a flat list).
  4. Press View Details on a run.
  5. Read the Execution Timeline — each step with a tick, a cross, or a skip symbol.
  6. Press View Details on a step to see the data that went in and came out.

05 · Expected result

The list shows one line per record — Completed, then the module and record reference, BACKFILL or the trigger that started it, how many times, how long ago, and how long it took.

Opening it shows the run’s status, when it started, how long it took, and a timeline of steps. There are three tabs:

TabShows
LogsThe timeline of steps
Cascade TreeWhether this run set off another workflow, or was set off by one
VariablesThe raw data the run worked with

06 · Troubleshooting and notes

Nothing here at all?

Either the workflow has never fired, or it is failing before it starts. Check that it is Active and that your trigger conditions are not too narrow. Remember that records filtered out by a trigger condition leave no trace — see Narrow a trigger with conditions.

Steps have technical names here

The timeline calls them module_event, action_flag and request_approval rather than "Record Created or Updated", "Flag" and "Approval". They are in the same order as your steps, so count down the list to find the one you mean.

A skipped step is not a failure

Open it and the Output Data usually says why.

Cascade Tree tells you if workflows are chaining

If it says this execution did not trigger another workflow and was not triggered by one, this ran on its own.

Variables is for support, not for you

It is the raw data in its original form, and it is useful when you are on a call with us.

Records are labelled by the module reference field

Which may not be the one you think of as the record’s name.

07 · FAQ

Common questions

How long are runs kept?

Older runs are cleared out over time. Do not rely on this as a permanent audit trail — the record itself keeps the decisions.

Can I see all workflows' runs in one place?

This page is per workflow. Open each one’s Logs separately.

What does the flag on a record tell me?

Click a flag on a record and it shows which workflow steps put it there.

Can I re-run a failed one?

Runs can be cancelled and retried from here. We could not produce a failed run to try it on, so what that looks like is not documented here.