Late flow runs appear despite CANCEL_NEW
collision strategy when worker or work pool has a concurrency limit
#16984
Labels
bug
Something isn't working
Bug summary
When using the CANCEL_NEW collision strategy, new flow runs exceeding the defined concurrency limit should be immediately canceled rather than queued. However, users are observing that flow runs still accumulate with a Late status when concurrency limits are set at the worker or work pool level, even though the deployment’s collision strategy is correctly configured as CANCEL_NEW.
This behavior suggests that the additional concurrency limits at the worker or work pool level may be interfering with the expected cancellation process, causing flow runs to remain in a Late state instead of being cleared out as intended.
Expected Behavior:
Flow runs that exceed the concurrency limit should be canceled immediately when CANCEL_NEW is set, regardless of additional concurrency limits on the worker or work pool.
Actual Behavior:
Instead of being canceled, excess flow runs remain in a Late state.
Steps to Reproduce:
Reproduction Example:
test flow
prefect.yaml file
To create the work pool, deploy the flow, and start the worker through the CLI:
Version info
Additional context
No response
The text was updated successfully, but these errors were encountered: