Diagnose Flow Runtime Errors

1. Reads the reported failure and the flow involved. This can be an internal server error on a flow-launched action or a runtime error when a Screen Flow launches from a meeting playbook stage.
2. Traces the root cause in the flow or its access settings. Causes found include:

• an input the framework passes but the flow never declared
• a missing Run Flows permission for one user
• an Assignment that replaced the notification recipient collection instead of adding to it

1. Applies the fix in metadata where it can. That means editing the flow XML and redeploying it, or converting the action to an object-specific action.
2. Hands the change to the user when the API or a deploy cannot make it. In one case the permission set sat inside a permission set group and the deploy hit a label conflict, so the user made the change in Setup.

To review a flow's logic before it fails, see Analyze Existing Flow Logic.