Description:
I’m experiencing unexpected behavior with a Power Automate Desktop (PAD) flow deployed via a solution.
Steps performed:
1. In a Power Platform production environment, I have a solution containing a PAD flow.
- The PAD flow includes a hard-coded version variable set to 1.0.
2. I delete the entire solution and wait for the confirmation that the deletion is completed.
3. I update the PAD flow and change the version variable to 2.0.
4. To be sure, I also save the Cloud flow that triggers the PAD flow.
5. I deploy the new solution (containing the updated PAD flow) to the production environment.
6. I run the PAD flow after deployment.
Actual result:
The PAD flow that starts is still reporting version 1.0, as if the old flow is being executed.
Expected result:
The newly deployed PAD flow with version 2.0 should run.
Question:
Has anyone encountered this behavior before, where an old PAD flow version keeps running after deleting and redeploying a solution? Any ideas on the root cause or how to force the correct version to run?
