Expected behavior: Using the Save as function creates a copy of the flow in the Team's environment that can be viewed in the PowerApps Teams app.
Actual behavior: The copy of the flow does not appear in the PowerApps Teams app.
Steps to reproduce:
The copy of the flow does not appear in the Build, Cloud Flows area. Opening the Power Automate app and changing the environment to the Team's environment does show the newly created copy of the flow, however.
Hello - Any update on fixing this bug? I will add that when save as is used, the original flow remains in the Build, Cloud Flows area and is not visible in the Power Automate app. Result is the original flow is only accessible from Build, Cloud Flows area and the copy is only accessible from the Power Automate app, Team's environment.
I'm running into the same thing when using the Save As feature to try to create a copy of a Flow in Power Apps for Teams. I don't see an error message or anything and the copy never appears in Teams. If I go to the Power Automate service in Office 365 and switch to the environment that my app is published in, I can see the newly created Flow under "My flows". I suspect this is related to how solutions work in some way because I'm not able to go into the default solution for the environment and add the Flow there.
Is there any workaround to this issue?
This seems like a bug.
When I log in to Power Automate Online (web) and switch to the environment of the team, the copy sits there.
However, that copy is not visable and therefor can not be used in the Teams environment