I had created a flow recently and have been customizing it. I set it to trigger on adds and changes to a SharePoint list. When it ran, I’d get an email from it. The only issue was I’d also get another email from a different flow with roughly the same content. I wasn’t supposed to get this second email. I could see it was from the first iteration of the flow and it didn’t have any of the new language I had included in the flow. I disabled the “good” flow just to be sure and, yes, I got another email from this old flow, so I knew there was another flow out there emailing me and monitoring the SharePoint list. The only issue was I couldn’t find it. I had two different IDs I sometimes use to create flow and I checked my cloud flows and “Shared with me” flows and there was nothing there except the flow I was working on.
Copilot suggested all the stuff I’ve already tried, and then it said there were some PowerShell tricks I could use, but I needed to be the Power Platform admin.
Ultimately, I found it by using the GUID of the sending flow. If you inspect the email header of the offending email, there is a line with the sending flow’s GUID like this
x-ms-mail-workflow: x-ms-workflow-name: 0c5bca93-d1f3-33d9-4b61-f24457b62b47;
So I copied that GUID, and opened up my “good” flow in my environment, then I replaced the part between “shared/” and “/details” with it.
This… https://make.powerautomate.com/environments/Default-b62ae4e2-d69f-4f11-9643-f9ccf49460e5/flows/shared/3b9e06cd-da54-48be-860d-756a12372fa1/details became https://make.powerautomate.com/environments/Default-b62ae4e2-d69f-4f11-9643-f9ccf49460e5/flows/shared/0c5bca93-d1f3-33d9-4b61-f24457b62b47/details
When I used that second URL, my “phantom” flow appeared and it showed a created and modified date that was several months in the past. I’m not sure what to make of this. I’d like to delete it, but I just disabled it. Problem solved for now.
Learning SharePoint 