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

is there any known issue with `create_flow_run` that will cause two flows to spawn from the one call?

i’ve a flow that does this:

```flow.terminal_state_handler = cycle_state_handler(...)```
where `cycle_state_handler` looks like this:
```def cycle_state_handler(project, **kwargs):
   """Re-runs `flow` once it reaches a finished state.

   Must be used as a `terminal_state_handler`."""
   def _handler(flow, final_state, _reference_task_states):
       if not isinstance(final_state, state.Cancelled):
           # set this to None to force the backend to make a new name for us
           prefect.context["flow_run_name"] = None

           create_flow_run.run(
               project_name=project,
               flow_name=flow.name,
               parameters=prefect.context.parameters,
               **kwargs
           )
       return final_state
   return _handler```

occasionally this handler spawns 2 flows instead of one. i track this by setting a parameter on the new flow to be the current flow run’s name and log said name when the child flow starts

Not particularly, maybe you can add another prefect log to see if it double calls the handler?

the `create_flow_run` task does that
```07:25:16 INFO prefect Creating flow run '&lt;generated-name&gt;' for flow 'main'...
07:25:33 INFO prefect Created flow run '&lt;generated-name&gt;': &lt;a url&gt;```

If there is only one log like that…i don’t think it would be that right?

they both are from the same call <https://github.com/PrefectHQ/prefect/blob/1.2.2/src/prefect/tasks/prefect/flow_run.py#L142-L168>

I know, but I mean together those just show one call from the logs right?

i can be more explicit and put one of my own at the start of the handler just in case, but i suspect it’ll just be verification of what that’s showing