Hi everyone. I noticed a new property under

prefect.yaml

schedules

object,

max_active_runs

. I don't see that field in this documentation: https://docs-3.prefect.io/3.0/deploy/infrastructure-concepts/prefect-yaml#schedule-fields What's the difference between that property and the deployment-level

concurrency_limit

property? In addition, I have both set to

1

but the deployment still spins up multiple flow runs with

Running

state, so it doesn't seem to be honoring my set

1

limit.

Hey Carlos! Thanks for helping us find that -

max_active_runs

is a relic of an abandoned syntax for deployment concurrency. Looks like we missed deleting it from a few places. 🙇

Got it. It was auto-added to my

prefect.yaml

as I deployed certain deployments, so I found it interesting.

Having the concurrency_limit set to 1 should do the right thing. What version of prefect are you on? I know @collin's been thinking about this recently so pinging him here.

Latest version, I did notice that after I went into the Global Concurrency tab, these were added. I assume these are auto-created when I set

concurrency_limit: 1

on the prefect deployment. However, they are set to Active=False by default, I had to enable Active myself through the UI and it seems to be working as intended now.

Hmm. That feels annoying though to have to go mark them as active after the fact.

Ah yes I believe that that inactive-by-default behavior is fixed in the upcoming release (which should be landing sometime today iirc) deployment concurrency limiting is still rather new and we've been fixing little rough edges like this.

Thank you both for your quick responses. Appreciate it.

thanks for raising @Carlos Cueto

Thank you! Sorry for the confusion. I also just tossed up an issue for that UI bug - thank you! i was also able to repro it. I"ll go check it out soon

@collin ++

Perfect. Thank you so much