Skip to main content
A run condition tells a computed column which rows are worth running. Rows that do not qualify are skipped, and a skipped row is never charged.
The Run conditions section of a column editor with Only run some rows turned on, two clauses joined by and, Add condition and Add condition group buttons, and a Generate button.

A column's run condition, built from two clauses.

​
Follow a saved view

Create a column while a saved view is applied. Run conditions opens with Only run rows in that view checked. The column follows that view. Editing the view’s filter then changes which rows the column runs on.

​
Save a filter as a run condition

A filter you have not saved as a view never becomes a run condition on its own. To keep it, open the filter panel and click Save as a run condition…. Pick the columns under Apply it to and click Save. This replaces any run condition those columns already have.

​
Turn on a run condition

Open the column’s editor and expand Run conditions. Check Only run some rows to start building a condition, and one empty clause appears.

​
Build the condition

Click Add condition for each rule, for example where Employees is over 50. Click Add condition group for a set of clauses with its own connector. Both grey out at eight clauses, groups included. Choose and or or once, on the second clause. Every top-level clause after the first follows that same connector.

​
Generate a condition from a description

Click Generate and describe the condition in words, like “the company is in the US and has more than 50 employees”. Oneprofile writes the condition for you, and a description it cannot turn into a condition says so instead of guessing.

​
Good to know

They are cleared and marked Skipped, rather than left holding an answer from an earlier run. A run never spends on a skipped row.
Yes, one level deep. The top-level connector is chosen once, and each condition group has its own, so you can build A and (B or C).
Only if it matches the clause builder’s shape. Otherwise it stays exactly as written, with a Remove button in place of the usual clause rows.
Any column that runs: enrichment, function or export. A plain typed in column has nothing to run, so it has no Run conditions section.
The view’s filter is copied onto the column as a normal run condition before the view is deleted, so the column keeps running on the same rows.
The column runs on every row. Check Only run some rows later if you want a condition again.
No. The clauses are hidden while Only run rows in is checked. Uncheck it, then check Only run some rows and build your own, and later edits to the view no longer apply.
Its filter includes something a run condition cannot express, like “has an error”. The checkbox is greyed out with the reason under it. If a followed view later gains such a filter, its columns keep the rules they had and stop following it.

​
Next steps

Run columns

See every way to start, watch and stop a run.

Schedule a re-run

Keep a gated column fresh on its own.