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, an Add condition button, and a Generate button beside them.

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

​
Turn on a run condition

1

Open Run conditions

Open the column’s editor and expand Run conditions.
2

Turn it on

Check Only run some rows to start building a condition. One empty clause appears.

​
Build the condition

1

Add a clause

Click Add condition for each rule, for example where Employees is over 50. It greys out at eight clauses.
2

Join them

Choose and or or once, on the second clause. Every clause after the first follows that same connector.

​
Generate a condition from a description

1

Describe it

Click Generate and describe the condition in words, like “the company is in the US and has more than 50 employees”.
2

Review it

Oneprofile writes the condition for you. 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.
No. One connector covers the whole condition, chosen once rather than clause by clause.
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.

​
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.