Viewing Runs

FlowMint Workflows → Run History lists every run, newest first, 30 to a page. You need the flowmint_manage_workflows capability to open it; administrators have it, and a site builder can give it to another role.

How to find a run

1. Open FlowMint Workflows → Run History.
2. To narrow the list, pick a status in All statuses, type a workflow id in Workflow ID, or both, and select Filter.
3. Select the run number, or View, to open the run.

The list shows Run #, Workflow, Form, Entry, Status, Duration and Created. A scheduled run has an empty form and the entry #0.

Run statuses

Status	Meaning
QUEUED	Waiting for the background queue to pick it up, normally within a minute.
RUNNING	Steps are running now.
COMPLETED	Every step succeeded, was skipped, or failed with on_error: continue.
FAILED	A step failed and stopped the run for good.
CANCELLED	Listed in the filter, but nothing in the current version sets it.

A run that stays QUEUED or RUNNING for a long time needs attention; see Troubleshooting.

Note

Promptless Forms’ Form Entries list also shows what your workflow did with the team email, in its Email column, with a link to the run. Needs Promptless Forms 1.12.0 and FlowMint 0.12.0.

Reading a run

The top of the run page shows Status, Workflow, Form, Entry, Created, Started, Completed, Duration and Retry count. A failed run adds Error code and Error message.

Under Steps, each step that started has a row with its number, Name, Type, Status and Duration. Open show in Output / Error to see the step’s output, or its error code and message.

Step status	Meaning
SUCCESS	The step finished. The output is what later steps can read.
SKIPPED	Its skip_if was true. The output names the condition.
FAILURE	It failed. The error explains why.
RUNNING	It is running now, or it started and never finished because the server stopped the process. Since 0.11.0 such a run is marked failed (interrupted) or retried.

Steps after a failure that stopped the run have no row. Steps inside a conditional or try_catch get rows of their own, numbered from 0 within their list, so the numbers repeat.

A completed run also has a Context snapshot: the form data, labels, entry, files, every step’s output and variables at the end of the run. Failed runs do not keep one.

What only the connector shows

The admin page does not show the settings each step ran with. Ask the assistant to fetch the run (flowmint_get_run): each step’s config_snapshot holds its config with placeholders filled in, so you can see the actual recipient, subject, folder name or URL. Conditions, nested step lists and import maps are kept as written.

What is kept, and for how long

Runs are kept until the workflow is deleted with its history, or the plugin is deleted with FMW_REMOVE_ALL_DATA set (see Installation and setup). There is no automatic clean-up. The records hold what the steps handled, including names, email addresses and other submitted values, and deleting the Promptless Forms entry does not remove them. Take that into account in your privacy notice and retention policy; see also Privacy and retention for the entries themselves.

Deleting a workflow keeps its runs unless the deletion asks for them to go too (cascade), which cannot be undone.

Related pages

• Replaying Runs — Run a finished run again after fixing what made it fail, what a replay repeats, and what you cannot do to a run that is still queued or running.
• Troubleshooting — Fixes for the problems people meet with FlowMint Workflows — runs that never start, blank values, conditions that misfire, email, Google Drive, Printavo and the connector.
• Failure Notifications — The alert FlowMint sends when a run fails for good — to Slack if a webhook is stored, otherwise by email — what it contains, and how to route or silence it.
• Error Codes — Every error code a FlowMint step or run can record, what usually causes it, and whether FlowMint treats it as retryable.