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.

[Nisha12]

We figured out that the changes were being triggered from a lower environment which still had an active flow. If your inactive flow is being triggered, it's better to submit a case with the NowSupport team as suggested above.