Dagster Cloud deployment settings reference#

This guide is applicable to Dagster Cloud.

This reference describes the settings that can be configured for full deployments in Dagster Cloud.

Refer to the Managing deployments in Dagster Cloud guide for info about configuring settings in the Dagster Cloud interface or using the dagster-cloud CLI.

Settings schema#

Settings are formatted using YAML. For example:


run_queue:
  max_concurrent_runs: 10
  tag_concurrency_limits:
    - key: "database"
      value: "redshift"
      limit: 5

run_monitoring:
  start_timeout_seconds: 1200

run_retries:
  max_retries: 0

Settings#

For each deployment, you can configure settings for:

Run queue
Run monitoring
Run retries

Run queue (run_queue)#

The run_queue settings allow you to specify how many runs can execute concurrently in the deployment.


run_queue:
  max_concurrent_runs: 10
  tag_concurrency_limits:
    - key: "database"
      value: "redshift"
      limit: 5

Property Description

run_queue.max_concurrent_runs

Property	Description
run_queue.max_concurrent_runs	The maximum number of runs that are allowed to be in progress at once. Set to `0` to stop any runs from launching. Negative values aren't permitted. Default - `10` Maximum - `500` ( Hybrid), `50` ( Serverless)
run_queue.tag_concurrency_limits	A list of limits applied to runs with particular tags. Default - `[]` Each list item may have the following properties: `key` `value` If defined, the `limit` is applied only to the `key-value` pair. If not defined, the `limit` is applied across all values of the `key` . If set to a dict with `applyLimitPerUniqueValue: true` , the `limit` is applied to the number of unique values for the `key` . `limit`

The maximum number of runs that are allowed to be in progress at once. Set to

to stop any runs from launching. Negative values aren't permitted.

Default -
```
10
```
Maximum -
```
500
```
( Hybrid),
```
50
```
( Serverless)

run_queue.tag_concurrency_limits

A list of limits applied to runs with particular tags.

Default -
```
[]
```

Each list item may have the following properties:

```
key
```
```
value
```
- If defined, the
```
limit
```
  is applied only to the
```
key-value
```
  pair.
- If not defined, the
```
limit
```
  is applied across all values of the
```
key
```
  .
- If set to a dict with
```
applyLimitPerUniqueValue: true
```
  , the
```
limit
```
  is applied to the number of unique values for the
```
key
```
  .
```
limit
```

Run monitoring (run_monitoring)#

The run_monitoring settings allow you to define how long Dagster Cloud should wait for runs to start before failing them in the deployment.


run_monitoring:
  start_timeout_seconds: 1200

Property	Description
run_monitoring.start_timeout_seconds	The number of seconds that Dagster Cloud will wait after a run is launched for the process or container to start executing. After the timeout, the run will fail. This prevents runs from hanging in `STARTING` indefinitely when the process or container doesn't start. Default - `1200` (20 minutes)

Run retries (run_retries)#

The run_retries settings allow you to define how Dagster Cloud handles retrying failed runs in the deployment.


run_retries:
  max_retries: 0

Property	Description
run_retries.max_retries	The maximum number of times Dagster Cloud should attempt to retry a failed run. Dagster Cloud will use the default if this setting is undefined. Default - `0`