Fixed- Flow not getting triggered (Callback Registration)– Power Automate / Dataverse

The out-of-the-box flow "Deserialization of Inspection Definition" was not getting triggered in one environment, even though it was turned on. The issue was caused by a failed operation called "CallbackRegistrationExpanderFilter" with an error message stating that the specified user is disabled. The solution was to turn off and turn on the flow, which would delete the old callback registration record and create a new one with the user who is turning off/on the flow. It was also observed that if the callback registration is owned by an enabled user, simply turning off and on the flow using a different user account will not delete the existing callback registration record, and it needs to be explicitly deleted.

Article 10m Nishant Rana's Weblog

---

Login now to access my digest by 365.Training

Login