Trail settings and workspace defaults
What a new trail starts with, who can fix stopped runs, a trail's own settings and version history, and trail limits on Agency.
By Operelio team · Updated October 31, 2026
On this page9
What a new trail starts with
An admin sets these under Trails in Settings. A trail started from scratch or from a workflow copies them when it is made. A template brings its own push setting and review. A copy of a trail brings that trail's checks, review and push setting. After that, each trail keeps its own, so changing these never changes a trail that already exists.
| Setting | Unless you change it |
|---|---|
| Wait for me if less than this much of the file gets through | 50% |
| Skip that on files smaller than | 20 rows |
| Wait for me if this many rows or more have a required value blank | 1 |
| When a run finishes and nothing is flagged | Hold every push for review |
| Bridgeant reviews the push | Off |
Two of the checks can be set to Never. Once you change a setting, Follow the recommendation puts it back to where Operelio starts it. With Bridgeant reviews the push on, The brief a new trail starts with sets the instructions.
Who can fix stopped runs
From Pro up, an admin chooses who can change a stopped run's settings, start it again, send it on with Send this one without a review, and put its fix on the trail: Admins only, or Everyone in the workspace. It is under Team in Settings, in the Permissions section, and it applies to every trail at once.
Only an admin can create a trail or switch one on.
A trail's own settings
On the canvas, click Trail settings. It has three tabs.
| Tab | What is there |
|---|---|
| Summary | What the trail does, written from the chain |
| Notifications | Who is told about the trail, and what they are told |
| Advanced | What happens with a workbook of more than one sheet, what happens when something goes wrong, the version history, and Delete trail |
The other settings are on the tiles and in the toolbar. The schedule is in the toolbar. The safety checks are on their tile. The push tile has three tabs: What gets created, Who gets each lead (the routing rules) and When it sends, which also holds how far your CRM can move before a held push comes back to you. The Scorecard and Map sources are tiles of their own.
When a file's columns change
A trail is for a source, so the next file can name a column differently, like Mail address for Email. The trail finds it and the run says which column it used. On the trail's page, Show settings has two sections for files whose columns change.
| Section | What it does |
|---|---|
| When a column is missing | For each step that reads a column: Stop the run, or Skip this step while the other steps run. Find & Replace skips unless you change it. Steps that decide which rows go on, like Deduplicate and Filter & Extract, stop. |
| Remembered columns | The names files have used for the trail's columns, each marked Found on a run or Picked on a run, with its date. The trail uses them on every file without asking. Remove forgets one. A column found on a test run isn't added. |
When a change takes effect
Most changes on the canvas are made on the Sandbox tab and reach the live trail when you press Put it live. Some save straight away: the name (click it at the top of the canvas, type, and click the checkmark), the CRM a trail pushes to, the record type, the watched folder and the saved mapping.
Version history
Advanced shows the version running now. See what changed lists the versions your runs used, up to 8, from the last 50 runs. Each shows what changed, with See the run for the first run on that version. The oldest one listed says it is the earliest version recorded here. Test runs are not counted.
What counts as a change: the steps, the email check, the Company Active Check, the formatter and its mapping, what the push sends, the push policy, the review and its instructions, and the safety checks. A new name, schedule, list of people, notification switch, or a change to how far your CRM can move while a push waits does not count, so a version that changed only those reads Nothing that changes what a run does.
On a trail Bridgeant built that you have edited, the trail's page offers Restore Bridgeant's original. A window lists each part that goes back, and the original goes in as a draft, never live, for you to test and put live.
When a trail earns a quieter setting
When a trail that holds every push has finished its last 3 runs without a problem, an admin sees Let clean runs send on their own on its page. Pressing it switches the trail to Send the clean ones straight away. Anything the checks or the review flag still waits for you.
Trail limits on Agency
On Agency, live trails and trails in total are shared by the agency workspace and all its client workspaces.
An admin of the agency can give a client its own lower limit, on the Clients tab on Home: open the menu on that client's row, choose Settings, then set Live trails and Trails in total. Leave either blank for no limit of its own. Defaults, at the top of the tab, sets what a new client starts with.
Lowering a limit pauses nothing. Until the client is under the new limit, it cannot switch another trail on, or, for Trails in total, make a new one.
Related
Frequently asked questions
Does changing a workspace default change my trails?
No. A trail keeps the settings it was made with. Change a trail's own settings on its canvas.
Why is a change I made not running yet?
Changes on the Sandbox tab do not run until you press Put it live.
Where do I choose who hears about a trail?
On the trail's own page: click Show settings under Trail settings, then go to Who hears about it.
Ready to get started?
Upload a file and run your first transformation. Free, no credit card required.