A trail's runs
Where to find a trail's runs, what each state means, what a run's page shows, and how long runs and their files are kept.
By Operelio team · Updated October 23, 2026
On this page7
Where to find them
Each file a trail picks up gets its own run, and so does a scheduled check that finds no new files. Every email about a run links to its page. You can also reach runs from four places. A single lead isn't a run: it has its own page, reached from the Leads tab, and leads gathered from a burst go through together as one list run.
| Where | What it shows |
|---|---|
| The trail's page | Recent runs, newest first: the last 10, test runs included with a Test run label. Click one to open it. |
| The canvas | Last run, Waiting for you and Runs this month, with Open the run history. Test runs are not counted here, but they still use jobs. |
| The Trails list | How many runs are held for review across all your trails. A trail's count opens its recent runs, and its row opens to show its report. |
| Home's Activity tab | Every run that started, test runs and skipped checks left out, alongside your tool runs and uploads. Filter by Trails, and click Open at the end of a run's row. |
| Leads, for single leads | The Leads tab lists every single lead from every trail, under To review, Held and All. A trail's page shows its last five under Recent leads, with Leads to see the rest. |
What each state means
A run's page and the trail's recent runs name the state in the same words.
| State | What it means |
|---|---|
| Running | The steps are working through the file. |
| Held | The push is waiting for someone to approve or discard it. |
| Stopped | The run could not finish and is waiting for a fix. |
| Sending | The push is being sent to your CRM, after an approval or on its own. The trail's recent runs show it as Running until it lands. |
| Starting again | The run has been changed or restarted and is queued to run again. |
| Finished | Nothing is left to do. A finished test run reads Finished too. |
| Failed | The run stopped and cannot be started again. |
| Discarded | The run was discarded, by someone or automatically. Nothing more happens to it. |
| Nothing to do | A scheduled run found no new files. |
| Not started | The workspace had used its jobs for the month. |
Held, Stopped and Failed are marked in amber.
What a run's page shows
The top of the page says what happened, when the run started, the folder and the CRM, and the trail version the run used. The link above it goes back to the trail, and Run history opens the trail's recent runs. Steps your plan left out are listed under What your plan changed.
| Card | What is on it |
|---|---|
| Why it stopped, Why it is waiting, Why nothing was sent, What it waited for, or for a test run, Why the push would have waited | The reasons, in order, with what you can do about them underneath. The title says where the run is now: stopped or discarded, waiting for you, finished with nothing sent, or approved and being sent. A note from the Bridgeant review is quoted as Bridgeant wrote it. |
| What this push would do | Before the push: what it would create, update and skip, how many of the updates replace a value your CRM already has, and what your CRM would refuse, worked out when it was held. To review counts the rows that wait in the Review queue, from your routing or the Scorecard, when there are any. On a test run nothing waits there, so it counts the rows that would. Not sent counts the rows the Scorecard held or dropped, and the addresses Quick clean left out, too. |
| What reached your CRM | After the push: what it created and updated, the rows that did not land, and the rows your CRM would not take, which were not sent. Not sent counts the rows the Scorecard held or dropped, and the addresses Quick clean left out, too. A run that never reached its push has neither card. |
| The file | Rows that arrived, rows left after the steps, values that look wrong (required values left blank, and emails or phones that aren't valid), and rows with no email address. For companies, rows with no website or name. On a run that stopped before its first step, all but Rows that arrived read Not reached. |
| Scorecard | Shown when the trail's Scorecard moved rows: how many it kept, sent to review, held and dropped. Left out when the run's reasons already say it. |
| What was different in this file | Shown when the file's columns weren't the ones the trail expected: a column it used in place of one it expected ("Used Mail address for Email."), a step it skipped because its column was missing, or a column it left out because two columns could each be it. A used column and a skipped step each link to the trail setting behind them. |
| How far it got | The chain as this run used it, including any change made to this run, with the stage it stopped or waited at marked. A file turned away before the first step reads stopped before the first step. |
| Rows that did not go | Shown when some rows did not reach your CRM, including the addresses Quick clean left out, each with why. Download the list gives you every row it can name as a CSV: on HubSpot, the first 500 refusals, and of Quick clean's, the first 1,000, with a last line giving how many it left out in all. |
What you can do from a run
A run that is still going, or one that has ended, has nothing to press. The exception is a finished run whose own change worked, which offers Put this fix on the trail.
| Button | On | Who |
|---|---|---|
| Approve and send | A held push, except a test run | Anyone in the workspace |
| Send it without a review | A held push whose first reason is that there is no usable review, except a test run | Anyone in the workspace |
| Discard this run | A held or stopped run | Anyone in the workspace |
| Change something about this run | A stopped run | Admins, unless the workspace allows everyone |
| Edit a step before the push | A stopped run where part of the push landed | Admins, unless the workspace allows everyone |
| Start this run again | A stopped run with a saved change that has not run yet, or one stopped because the review could not run | Admins, unless the workspace allows everyone |
| Send this one without a review | A run stopped because the review could not run | Admins, unless the workspace allows everyone |
| Put this fix on the trail | A run whose own change has been shown to work | Admins, unless the workspace allows everyone |
The setting is Fixing a stopped trail run, under Team in Settings, in Permissions. If a push came back because your CRM moved, switch on "I have seen what changed. Send it anyway." before you click Approve and send.
How long runs are kept
Runs are not deleted, even when their trail is.
A held push waits until someone approves or discards it. A stopped run nobody fixes is closed as Failed after 14 days. A finished test run is discarded after 14 days.
The files follow your plan's retention. A file a run is still using, because the run is going, held or stopped, is kept until the run ends. Once a run's output file has gone, Rows that did not go no longer shows each row's email address or website, or the addresses Quick clean left out, only how many.
A single lead's details, the cells that arrived with it, go after the same time, counted from when it arrived. Its page keeps what happened: its score, its route, what reached your CRM and its timeline. A lead still waiting when its details go can't be sent any more, so it is dropped, with a line saying why.
| Plan | Files kept for |
|---|---|
| Free | 24 hours |
| Starter | 30 days |
| Pro | 30 days |
| Agency | 90 days |
The trail's report
On the Trails list, open a trail's row to see what it has done since it was last switched on. Test runs are not counted here, but they still use jobs.
| Figure | What it counts |
|---|---|
| Runs | Every run since the trail was last switched on |
| Rows in | The rows that arrived, across every run |
| Created | Records the trail's pushes created in your CRM |
| Updated | Records the trail's pushes updated in your CRM |
| Jobs used | One per finished stage |
A push still waiting for approval is not counted in Created or Updated until it is sent.
Related
Frequently asked questions
Why do the canvas and the trail's page show different numbers of runs?
Runs this month on the canvas counts real runs since your billing month began. The trail's page lists the 10 newest runs of any age, test runs included.
Does discarding a run undo a push?
No. Discarding stops a held or stopped run going any further. Rows a partial push already sent stay in your CRM.
Can I see runs older than the last 10?
Not from a list. The trail's page lists the 10 newest. An older run still has its own page, linked from the emails about it.
Ready to get started?
Upload a file and run your first transformation. Free, no credit card required.