Is there a built-in way to set a maximum number of queued runs for a given (.e.g) pipeline? Do I need to create a custom launcher for this?

Hi Ben - you can set per-tag limits to accomplish this, see the example here: https://docs.dagster.io/deployment/run-coordinator#run-limits

My understanding is that this limits the number of concurrent runs, not the number of queued runs, right?

Oh, maybe I don't understand the use case. What are you hoping will happen to runs that are submitted when there are already that many queued runs, a failure?

Probably a cancellation? My issue is that some jobs are idempotent, so repeating them in unnecessary. It’d be nice to be able to express this in dagster so that certain jobs are queued at most one time. That was my thinking, at least. It sounds like defining a custom coordinator would be the best course of action here?

Yeah, a custom run coordinator would probably be the way to go there

Alright - thanks for your help, Daniel