> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getoneprofile.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Set a run condition

> Gate a column so it only runs on the rows that qualify, and skip the rest at no cost.

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.

<Frame caption="A column's run condition, built from two clauses.">
  <img src="https://mintlify.s3.us-west-1.amazonaws.com/oneprofile/images/tables/run-conditions.png" alt="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." />
</Frame>

## Turn on a run condition

<Steps>
  <Step title="Open Run conditions">
    Open the column's editor and expand **Run conditions**.
  </Step>

  <Step title="Turn it on">
    Check **Only run some rows** to start building a condition. One empty clause appears.
  </Step>
</Steps>

## Build the condition

<Steps>
  <Step title="Add a clause">
    Click **Add condition** for each rule, for example where Employees is over 50. It greys out at eight clauses.
  </Step>

  <Step title="Join them">
    Choose **and** or **or** once, on the second clause. Every clause after the first follows that same connector.
  </Step>
</Steps>

## Generate a condition from a description

<Steps>
  <Step title="Describe it">
    Click **Generate** and describe the condition in words, like "the company is in the US and has more than 50 employees".
  </Step>

  <Step title="Review it">
    Oneprofile writes the condition for you. A description it cannot turn into a condition says so instead of guessing.
  </Step>
</Steps>

## Good to know

<AccordionGroup>
  <Accordion title="What happens to rows that don't match?">
    They are cleared and marked Skipped, rather than left holding an answer from an earlier run. A run never spends on a skipped row.
  </Accordion>

  <Accordion title="Can I mix and and or in one condition?">
    No. One connector covers the whole condition, chosen once rather than clause by clause.
  </Accordion>

  <Accordion title="Can I edit a condition after generating it?">
    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.
  </Accordion>

  <Accordion title="Which columns can have a run condition?">
    Any column that runs: enrichment, function or export. A plain typed in column has nothing to run, so it has no Run conditions section.
  </Accordion>
</AccordionGroup>

## Next steps

<CardGroup cols={2}>
  <Card title="Run columns" icon="play" href="/tables/run-columns">
    See every way to start, watch and stop a run.
  </Card>

  <Card title="Schedule a re-run" icon="calendar-clock" href="/tables/scheduled-reruns">
    Keep a gated column fresh on its own.
  </Card>
</CardGroup>
