flowstudio-power-automate-debug

Use the FlowStudio MCP tools to list flow runs, find the failed run, then call get_live_flow_run_error to read the error. The last entry in failedActions identifies the root-cause action, which you inspect with get_live_flow_run_action_outputs.

Call get_live_flow_run_error on the failed run and read the failedActions array, which is ordered outer-to-inner. The last entry is the root cause; then inspect upstream action outputs to find null values or wrong field paths.

InvalidTemplate errors occur when an expression receives a null value, uses a wrong field path, or gets a type mismatch such as an object where an array is expected. Fixes include wrapping values with coalesce() or correcting case-sensitive field names.

Yes, expression and data logic issues can be fixed by fetching the definition with get_live_flow, editing the action inputs, and calling update_live_flow with the definition and connectionReferences. Connection authorization failures still require the designer.

ConnectionAuthorizationFailed means the connection referenced in the flow is owned by a different user or service account than the one whose token is being used. It cannot be fixed via API; re-authenticate the connection in the Power Automate designer.

You need a FlowStudio MCP subscription with a valid JWT token and the environment ID containing your flows. Subscribe at https://mcp.flowstudio.app and call tools/list first to confirm available tool names and parameters.