Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

Howdy, y'all!

It appears that when a flow has a new version registered, any flows scheduled to run are cancelled.

This occasionally breaks one of our larger flows (Prefect 1.0, we run many flows from one big flow) when our flow schedules another flow, but that flow hasn't started yet. Would there be a way to workaround this?

Hey Jeffrey! You are testing my memory here, but maybe try with setting an idempotency key in the register method

`idempotency_key (str, optional)`: a key that, if matching the most recent registration call for this flow group, will prevent the creation of another flow version and return the existing flow id instead.

I'm not positive that will have the desired effect but as it causes the flow_id to remain the same it may also persist scheduled flow runs

Thanks! Upon further inspection -- we did do this, but it was broken.

If anyone else has any thoughts here, I think we'd like to guarantee it never happens. Best idea I have is to block off a time to register flows.