Hi. The docs seem to currently suggest two different ways of limiting concurrency using tags: • https://docs.dagster.io/guides/limiting-concurrency-in-data-pipelines#limiting-specific-runs-using-tags • https://docs.dagster.io/deployment/dagster-instance#run-coordinator (you'll have to click the inline tabs to get to the relevant examples) Any preference between the two, and/or should the docs be updated for one example to reference the other approach?

run_queue:
  max_concurrent_runs: 15
  tag_concurrency_limits:
    - key: "database"
      value: "redshift" # applies when the `database` tag has a value of `redshift`
      limit: 4
    - key: "dagster/backfill" # applies when the `dagster/backfill` tag is present, regardless of value
      limit: 10

run_coordinator:
  module: dagster.core.run_coordinator
  class: QueuedRunCoordinator
  config:
    max_concurrent_runs: 25
    tag_concurrency_limits:
      - key: "database"
        value: "redshift"
        limit: 4
      - key: "dagster/backfill"
        limit: 10

Hey Jens! Thanks for pointing this out - I think the second example (run coordinator page) was missed when I made that concurrency guide. I’ll get that updated. Having a top-level

run_queue

key like that in the first example will enable the

QueuedRunCoordinator

and apply any tag limits you’ve defined.

Great! Thanks for confirming 🙂