Safety checks and held pushes
The checks a trail runs before every push, the ones you can set, what a held push looks like, and what approving it does.
By Operelio team · Updated September 2026
On this page8
What the checks do
Before every push, the trail looks at what the push would do and holds it for your approval if something looks wrong. The checks are free. You set two of them, and one of those has a small-file exception. Nine are always on. The Bridgeant review is a separate check you can add.
A held push waits until someone approves or discards it. Nothing reaches your CRM in the meantime.
The two you set
Set them on the trail's Safety checks tile, under What you can set. New trails start from your workspace defaults, under Trails in Settings. Changing the defaults never changes a trail that already exists.
| Check | Unless you change it | Can be switched off |
|---|---|---|
| Wait for me if less than this much of the file gets through | 50% | Yes, set it to Never |
| Skip that on files smaller than | 20 rows | No. It only applies while the check above is on. |
| Wait for me if this many rows or more have values that look wrong | 1 | Yes, set it to Never |
The smallest files are skipped because on a short file a few rows are a big share. Losing 2 of 5 rows is 40% and means nothing.
The ones that are always on
Every trail holds its push in these cases. Each is a case where sending anyway is worse than waiting for you.
| Case | Why it waits |
|---|---|
| A file we could not screen | The file could not be checked against your Do Not Contact list. |
| CRM settings we could not read | Without them, we cannot tell which rows the CRM would refuse or which values would be replaced. |
| Rows your CRM will refuse | Some rows would be turned away by the CRM. |
| Replacing a value your CRM already has | The push would write over values already in the CRM. |
| An owner we could not resolve | We could not read the people in your CRM, so the owners in the file's owner column could not be checked. |
| An owner your CRM does not have | Rows name an owner who is not a user in your CRM. |
| People we could not read | We could not read the people in your CRM, so the rows could not be shared out between them. |
| People no longer in your CRM | Some of the people the trail shares its rows between have left the CRM. |
| A workbook with more than one sheet | The trail used one sheet. Check it was the right one. |
The Bridgeant review
Bridgeant review is off unless it is switched on and given rules, by you, your workspace defaults, the template you started from or the trail you copied. It reads a summary of what the push would do, never the values in your file, and it can only hold a push. It never sends one. Each review that runs costs one Bridgeant message.
If the review cannot run because the workspace has no messages left, messages are paused, an agency's limit for this workspace is used up, or your instructions are too long, the run stops and says what to fix. If there is no usable review for another reason (it timed out, failed, or its answer could not be used), the push is held and the page says so. If that is the first reason listed, the button reads Send it without a review.
A held push
The people who hear about the trail are told in Operelio and by email, with a Review this push button. The run's page shows why it is waiting, how far the run got, the file, and what the push would do, worked out against your CRM when it was held.
Anyone in the workspace can approve or discard a held push.
| Button | What it does |
|---|---|
| Approve and send | Works the push out again against your CRM as it is now. Then it sends it, holds it again if something has moved, or finishes without sending if every row is already up to date. |
| Discard this run | Ends the run. Nothing is sent, and the trail does not pick that file up again. |
When approving holds it again
A held push can wait for days, and your CRM keeps changing. So approving checks again, and the push comes back to you if any of these is true:
A row would now replace a value it did not before
Even one row.
A new reason to hold turns up
A safety check that did not fire the first time. Bridgeant does not review it again.
Too many rows would now do something different
10% of the rows or more unless you change it, and never fewer than 3 rows. Set the share on the push tile's When it sends tab, under Hold it again if this share of rows would now do something different.
The trail points at a different CRM connection, or the file changed
A reconnect counts as a different connection.
When it comes back because rows changed, the page says what changed. To send it, switch on "I have seen what changed. Send it anyway." and click Approve and send. When it comes back for anything else, check it and approve it again.
How long things wait
A held push, other than a test run, waits until someone approves or discards it. It does not expire, and its files are kept until then.
A stopped run nobody fixes is closed as Failed after 14 days. Upload the file to the folder again to run it.
A finished test run is discarded after 14 days if nobody discards it first.
Deleting a trail discards its held pushes and stopped runs.
Related
Frequently asked questions
Can I switch every check off?
You can set the two you control to Never. The always-on cases stay on for every trail.
Can Bridgeant push something the checks would hold?
No. Bridgeant can only hold a push. It never sends one.
Who gets told about a held push?
The people on the trail's list of who hears about it. If the list is empty, or nobody on it is still in the workspace, the workspace admins. A test run that ends with a push to show tells nobody.
Ready to get started?
Upload a file and run your first transformation. Free, no credit card required.