Recently, we faced an interesting issue, where we updated an existing flow in our Dev, basically we removed the Filter Rows condition and deployed it to UAT.
Before –
Now –
In our Dev, it was working fine, getting triggered on the update of the field specified in the Select Columns; however, after deployment to UAT, it was still getting triggered only on the old filter condition, which we had already removed.
Turning off and on the Cloud Flow didn’t help.
The client data did not have the Filter rows condition.
Interestingly, we can still see the filter expression existing for the callback registration record of that flow in our UAT.
Eventually, we deleted the Callback registration record, turned the flow off and on, and it created the correct Callback Registration record with filter expression as null this time.
This fixed the issue, and our flow got triggered correctly.
More on Callback Registration –
Fixed- Flow not getting triggered (Callback Registration)– Power Automate / Dataverse
Hope it helps.
Discover more from Nishant Rana’s Weblog
Subscribe to get the latest posts sent to your email.
Share It –
