Hi, I noticed this situation several times last week. During the registration of an updated Flow, we have notification of 10 flow runs with the status of a Cancel arrival. It looks as if in the process of registration he creates a new flow (canceled flow has a different id), then realizes that such a flow already exists and makes cancellation of its 10 scheduled launches, and then updates the old flow. This is not critical, but maybe someone else has encountered it. We use Cloud.

@Marko Herkaliuk Every state (such as Canceled) has a message attached to it. Can you share it? It's in your flow logs. Normally, flows only reach the state Cancelled if the user explicitly cancels the flow from the UI, CLI or API.

@Anna Geller message was Run 

rebel-rat

 of flow 

Mailkeeper Receiver Tests

 entered state 

Cancelled

 with message 

Flow bd19be8d-d5e9-4fd5-9799-f666fb599dcd was archived

.

I’d say that you can ignore it - it’s seems that the Scheduler service tries to be super informative and gives you more details about which flow runs does it schedule or unschedule, and in your case it even seems to be quite useful - it tells us that due to a new Flow version that got registered, the old runs are Canceled because their corresponding Flow was archived. But if it bothers you, I could ask the team to look for more details about it. LMK

In principle, I don’t care much about it, I just decided to share the fact that sometimes it sends logs informatively, it’s interesting that it happened only a few times during the whole time.