Fix a stopped run

A held run reached the push and is waiting for someone to approve it. A stopped run could not get that far, or only part of its push landed, and it waits for a fix. A failed run cannot go any further.

The page says the run stopped before sending anything, or that part of the push reached your CRM, and Why it stopped lists the reasons. The buttons depend on why it stopped.

Change something about this run opens the run's own settings. A change applies to this run only, and the trail is not touched.

When the file is missing columns, the page offers one fix straight away: run it without the steps that need them, for this file only. Change something else about this run opens the rest.

The run starts again at the first stage your change affects, or where it stopped if that comes first. Stages before that point are reused and not charged again. From there, the steps, Company Active Check, Verify emails and the formatter each use one job when they run again. The push and the review use none.

If the run goes through Verify emails again on Full check, it holds verify credits again. If the Bridgeant review runs, it uses one message, unless the review already ran on this run and you changed only Before it sends.

In the editor, once you change something, Change something else about this run shows a Starting it again panel with the jobs, verify credits and Bridgeant message a restart uses. The buttons on the run's page show no costs.

A run that starts again from the push can wait up to fifteen minutes before it continues.

The rows that did not go are listed on the run's page, and Download the list gives you every one. You cannot send just those rows again.

Edit a step before the push lets you change The steps or Verify emails, and the whole file goes through once more. Rows that match a record already in your CRM then follow the trail's push settings. A change only to Before it sends, or to Safety checks and Bridgeant, is refused, because it cannot send those rows again.

If the workspace had no Bridgeant messages left, messages were paused, or an agency's limit for the workspace was used up, fix that first, then click Start this run again. It picks up where it stopped. If a change is saved on the run, it starts from wherever that change takes effect.

Send this one without a review turns the review off for this run only and starts it again. If the trail holds every push for review, the push then waits for approval.

If the review instructions are too long, click Send this one without a review, or shorten the instructions on the trail, upload the file again, and discard this run.

A change you make to a run stays on that run. If every run should work the same way, put it on the trail once the run shows it works.

Put this fix on the trail appears on the run's page after the run's change has run. The run must have finished, be held, or have stopped again after the stage you changed. A change to Before it sends, the safety checks or Bridgeant needs a finished or held run, or one where part of the push landed.

It changes the trail for every run after this one, as a new version. If the fix turns the Bridgeant review off, the page says that putting it on the trail turns the review off for every later run.

The button does not appear when the run finished with nothing to send, was a test run, or its fix is already on the trail. If that part of the trail has changed since the run started, clicking it is refused, and the page says why.

A stopped run is closed as Failed after 14 days. Its file is not picked up again by itself. Upload the file to the folder again to run it.

One stopped run does not stop the trail. The same file problem at the same stage twice, with no finished run between, sets the trail to Needs attention, and so does a problem with the trail itself, the first time. Missing columns, a review that could not run, a partial push and a test run never do.

Anyone in the workspace can discard a stopped run. By default, only admins can change it, start it again, send it on with Send this one without a review, or put its fix on the trail.

From Pro up, an admin can let everyone do these: set Who can change a stopped run's settings to Everyone in the workspace, under Team in Settings.