Deleted flow still running

[stephanb]

So we have multiple flows for creating Sharepoint folders and document locations that are triggered by either Create or Update of a CDS record. We had an earlier version that was flawed and it would not work correctly with a sub flow, so we created a new one and deleted the old one.

The problem now is that the old flow is still running, and it's causing us problems. I've tried going thru all flows, trying to find the one where it triggers. Ive check 'my flows', 'team flows', our solutions and even gone thru the resources on environments in the admin center. I cant find the old flow. It should be the one that is deleted, because the document location it creates has the description defined in the old flow.

Is there any way get the log of what flows have been running? and is there a way to permanently delete the old flow?

I have tried making a flow that iterates thru all flows as admin, to see if i could find it. But in that case power automate doesn't authorise our admin user during authentication so I cant find the environment inside flow.

[mcin9781 · Accepted solution]

Have you checked with your team to see if someone else owns the flow you are referring to?

You also may be able to use the Power Automate Management connector in order to list all the flows you have admin access to.

https://docs.microsoft.com/en-us/connectors/flowmanagement/

Also there is a PowerShell Script that you can run in order to get all flows in an environment 

https://docs.microsoft.com/en-us/power-platform/admin/powerapps-powershell

If that does not work for you and you are not able to find the deleted connector and nobody from your company has any idea where it is located,  you should open a support ticket to see if they are able to resolve the issue on the backend. 

[stephanb]

Hi,

I've tried using the connector and I've made a powershell script that returns all flows still could not find it.

So I made a second attempt to find out if there was something I missed in one of the running flows. And it turns out that the deleted flow is using one of the sub flow from our dev environment for sanitizing strings.

Is there a way to see what triggered the subflow?

I've contacted MS support for this issue, but its taking time so I just want to make sure that I have made every possible effort from my end.

[Mira_Ghaly]

Hi @stephanb

Please try to login to flow Admin center, from there you can see all the flows and you might also see a duplicates for the same flow so make sure they are all deleted from Flow admin center. 

If this solves your problem please mark as a solution

[stephanb]

Hi @Mira_Ghaly ,

I Have already tried that, I can not find the flow thru admin center, "my flows", "team flows", In any solution, in any environment.
and also tried as mentioned above to write a powershell script to get every flow the admin has access to, still nothing.

If there is no other way to find them i guess preying to the support gods is the best alternative i have 😂😭

The only relation to the ghost flow i have found is that it is using one of my subflows every time it runs.

[Mira_Ghaly]

@stephanb

ON Admin center there is Load More at the bottom can you make sure you click it till it is not there to make sure all flows are loaded. 

Also can you try to check on your default environment it might be triggering from there. 

[stephanb]

@Mira_Ghaly, which admin center are you reffering to? 

I have checked resources for in the "flow admin center" and in the "Power app admin center". Still cant find the flow.

[Mira_Ghaly]

@stephanb I am referring to flow admin center, have u checked ur default environment for My flows and Team flows? 

[stephanb]

@Mira_Ghaly , Yes I've tried that, Still nothing.

After a chat with support here now it seems like they can't find it either, they have mobilised some backend team to fix this. Apperently this issue has occured before, where they can't find the flow anywhere, but its still running.

Response from support: "I have been checking the background data and not found anything. I spoke to a colleague and he has seen a similar case where a Flow had already been deleted but somehow was running, so they had to find the Flow and disable it. I am engaging the backend team however they are in a different region so it might take some time to get back to me."

[Mira_Ghaly]

@stephanb 

Yes it happened with me last week but i was able to find from where it is running through the flow admin center.

Also i am not sure if you are using the CDS connector or the CDS (Current Environment) , if you are using the CDS Connector i am sure it causes some issues during deployment across environments. Good Luck and Hope this gets fixed!

[ychuan156]

Hi @stephanb, you can access the running flow from "Monitor" -> "Cloud flow activity" -> Find the flow run and click on it to access the flow detail page. You can then get the flow ID from your browser address bar from the portion after "flows/". It is a GUID. Then, you can do Power Automate Management - Connectors | Microsoft Docs -> Delete Flow passing in this GUID as flow name. I managed to delete one of my "deleted hidden" flow like this.

[stephanb]

Hi @ychuan156,

At the time of this issues we ended up resolving it by turning them all the flows we could find in the admin panel off.

After this we used a Powershell script to find the GUIDs of the (still) active flows, that we were unable to see in the Admin panel, then another Powershell script to disable these flows. Linkes provided by @mcin9781

The issue was that we had multiple versions of the same flow active and was unable to see them in the admin panel.

We have not experienced the same issue in 2 year.