
Announcements
This has been an issue for some time now, but it has only seem to become worse for apps in solutions.
I have 4 flows in the solution. (even after I add dependencies for the Power App), but in the actions section (and power apps) there are duplicates of existing flows, as well as old flows that has not been part of the app or the solution for a long time. (Another issue is that I can't really see the whole name of the flow in the list, and the list can't be expanded, the only way to find it is to use the browser inspector tool). This is a somewhat annoying issue that has been here a while, anyone know of a workaround for this issue? Seems PowerApps Studio bugfixes are really low priority 😕
I have cleared my cache and settings without this making any difference. I guess one workaround is to export the power app and unpack it and edit the code, but that seems needlessly complicated.
The screenshots show that they are duplicates as they are both highlighted when adding and removing them. The ones covered in red are no longer listed in this app and this solution and has not been part of it for a long time.
Duplicates and stale flows
Flows added to solution
one workaround is to export the power app and unpack it and edit the code
I think for me this does not work, because the modification of any files manually such as with an attempt to be unzipping, editing, and rezipping of msapp file, is not accepted and the upload will fail on the manually modified file even if it is packed back exactly correctly. So I don't think that workaround even works. If you tried it and it works tell me because when I tried it that doesn't work. I do not know if there was some point this worked but from some years now that kind of modification of the files does not work and will be rejected on attempt to upload the file even if the structure is exactly correct. I suspect it doesn't work because probably it is not desired for there to be a way modify the files from outside Power Apps such as with a 3rd party editor or something like that, it is just my speculation though.
Anyway regarding why you see this, I am not exactly sure how to resolve in this case. (careful when testing this, use a non-important or dev Flow here) If the Flow is saved as a new copy of it, the other one deleted, the new one added to Power Apps, does this help clear some of the other ones out?
I would be curious as well how to mitigate this, sometimes I could see why it may help to be easy to take those out of the list in a simple and quick way.