That message usually means the limit definition is editable, but the live counters are not. In Prefect Cloud,

active_slots

and

denied_slots

for a global concurrency limit can be served by the orchestration cluster, so trying to write those values directly will fail with the error you saw. What’s going on -

limit

,

enabled/disabled

, and

slot_decay_per_second

are configuration -

active_slots

and

denied_slots

are runtime counts - In your Cloud setup, those runtime counts are managed by orchestration, not manually writable from that form/update path So if you’re trying to “reset” the counters by editing the limit and setting

active_slots=0

, Cloud rejects it. What to do instead 1. Update only the definition fields Remove the count fields and only change things like: -

limit

- enabled/disabled -

slot_decay_per_second

2. If slots appear stuck Usually that means a lease/run/session that acquired slots has not been released yet. The count should clear when: - the run exits cleanly - the lease expires - decay reduces the count over time, if decay is configured 3. Practical workaround if you need a hard reset now If this is operationally urgent, the simplest workaround is often: - disable/delete the existing global concurrency limit - recreate it with the desired configuration Be aware this changes the object rather than mutating the live counters. CLI commands I verified the CLI group exists in Prefect 3.x: -

prefect global-concurrency-limit inspect

-

prefect global-concurrency-limit update

-

prefect global-concurrency-limit delete

-

prefect global-concurrency-limit create

Examples:

bash
prefect global-concurrency-limit inspect my-limit

bash
prefect global-concurrency-limit update my-limit --limit 10

bash
prefect global-concurrency-limit disable my-limit

bash
prefect global-concurrency-limit delete my-limit
prefect global-concurrency-limit create my-limit --limit 10

Important note The CLI help currently still shows

--active-slots

on update/create, but the error you’re seeing indicates your Cloud backend will not accept writes to those runtime count fields in this context. Useful docs / entry points - Prefect Cloud: app.prefect.cloud - Prefect docs: docs.prefect.io If you want, I can help you figure out whether your limit is actually stuck versus just non-editable, and suggest the safest reset path based on the exact limit config and what

inspect

returns.

@Marvin ^

If you paste the output of:

bash
prefect global-concurrency-limit inspect <limit-name>

I can help interpret it. If you just want the quickest next step, try:

bash
prefect global-concurrency-limit disable <limit-name>

and, if needed, recreate it:

bash
prefect global-concurrency-limit delete <limit-name>
prefect global-concurrency-limit create <limit-name> --limit <n>

Since the counters are orchestration-managed in Cloud, that’s usually the cleanest way to “reset” when the UI won’t let you write

active_slots

/

denied_slots

directly.