BUG: When using "Set State" for flow-run, it interrupts with other flow-runs

[trinebrockhoff]

Bug Description When having a flow say: MyFlow.

If starting for a run of this flow, called flow_first_run. Say it runs through but fails.

If I then run another instance of the flow, called flow_second_run, and while that is running, I set the state of the previous flow, flow_first_run to be "Skipped". Then flow_second_run is interfered, and will not run as it should.

Browsers Tested:

• [ ] Chrome

[zhen0]

Hi @trinebrockhoff - thanks for the ticket. Can I check some information here:

• You have two flow runs from the same flow
• If you change the state of flow-run 1 while flow-run 2 is running, you are seeing it affect the state of flow run 2?
• Are you using the set-state dropdown?

I can't re-create this and the set-state drop down (and the set state mutation it calls) are based on flow run ids so I'm not sure how this would happen. If you can give some info and ideally a reproducible example, I'm happy to investigate further