Worker picks up AwaitingRetry
flow runs waiting to execute decorator-defined retries if retry_delay_seconds
exceeds worker's polling window
#15458
Labels
bug
Something isn't working
Bug summary
This is harder to reproduce on cloud, but happens consistently on a local server.
Deploy this flow to a work pool (what the task functions do doesn't matter, this is just to match the included screenshot):
After the first failure, 30 seconds will pass and the flow will be retried in its first process, but the worker will also pick up the flow run again and start a new process/container, running only what it believes to be the remaining retry.
The final outcome is a run count of 3, even though it should run two times at most.
Version info (
prefect version
output)Additional context
I was not able to reproduce this with a served flow.
The text was updated successfully, but these errors were encountered: