Starting criteria
The components that decide whether a new crawl run may start.
Starting criteria gate whether a new run is allowed to begin. A job lists them under config.starting_criteria. This page catalogs the available kinds and their parameters.
How starting criteria are configured
Each entry in config.starting_criteria is an object with a kind and an optional params object. A starting criterion is checked before a new run begins and can refuse to start it. This is most useful for jobs with triggers that may fire while a previous run is still active.
config:
starting_criteria:
- kind: exclusive
params:
by: job_id
limit: 1exclusive
Limits how many runs may be active at once, preventing overlapping runs. A new run is refused while the active count for the chosen grouping is at the limit.
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
by | tenant_id, job_id, or labels | no | labels | The grouping the active-run count is measured over. |
limit | integer | no | 1 | The maximum number of active runs allowed in the grouping. |
starting_criteria:
- kind: exclusive
params:
by: job_id
limit: 1