Hi folks, question about the lazarus process. Why would lazarus try to reschedule a flow run if it reaches a successful state ?

Could you DM me the flow run ID of this flow so that I can cross-check? In general, Lazarus is typically only rescheduling flow runs in case of some infrastructure issues (e.g. if your pod crashed). This is indeed a bit puzzling given that the flow run seems to have been successfully completed.

(sent) thank you for taking the time to look into this

as a workaround, you could disable Lazarus for this flow as described here

yes sure

Gotcha. Could it be that there are some unclosed DB connections or other resources like HTTP clients that you use in your flow? I saw a similar issue occurring due to resources failing to close/shut down. I’m also wondering if the concurrency limits you use may be related to this. I don’t see any clear indicators why this may be happening and would open a Github issue for now and suggest to disable Lazarus for this process as a workaround until then

Could it be that there are some unclosed DB connections or other resources like HTTP clients that you use in your flow

there are no DB connections, just a call to the prefect KV store to add a key and then remove it