Inactive flow still triggering

[spike]

I have an odd flow related problem. I've inactivated two flows (last month) but it turns out they are still being triggered. 

This is the flows:

But as you can see from the execution list they are still triggering now:

Does anyone know why this might be happening? Any ideas on what I can look at?

I could delete the flows, but that feels like a sledgehammer to crack a nut. Feels like there's a bug somewhere?

(I inactivate the flow using the flow designer, captured it in an update set, and then moved it to our prod instance.)

Thanks.

[Dr Atul G- LNG]

Hi @spike 

Better to log a HI case. 

Dont delete the flows, that is not recommended and cause major issue. Or try to directly deactive  on prod and test.

[Nisha12]

@spike 

We are facing the same issue where our flow is inactive, but is still being triggered. Have you figured out a solution yet? 

[spike]

I'm afraid I do not. The flows are still there so I didn't delete them. And I didn't raise a ticket to ServiceNow either. Looked back through my releases and while I can see stuff was changed I don't recall what. Sorry..

[anandvk222]

Got any solution on this?