A code app runs an instant cloud flow through its generated service. The flow's run history shows success and the expected value is computed, but result.data in the app is always empty. What is the most likely cause?
Select an answer to reveal the explanation.
Short Explanation
A flow is like a coworker who finishes the job but never calls you back. Unless the flow ends with a Respond to a Power App or flow action, there's nothing for your app to receive. Don't blame CSP or async behavior when the flow just never answered.
Full Explanation
A cloud flow started from a Power Apps trigger returns data to its caller only through the Respond to a Power App or flow action, which defines named outputs and their values. When a code app adds the flow, the CLI builds the generated models from the flow's OpenAPI definition, including those outputs, and the Run method's result exposes the response in its data property. A flow that computes a value but never responds completes successfully with nothing to return, so data stays empty. Input schema on the trigger shapes the parameters the app sends; its absence does not cause outputs to be discarded. Code apps do receive a typed response from the flow when one is defined, so there is no requirement to persist results in Dataverse for the app to read. CSP governs requests the app's own code makes to external origins; flow calls go through the generated service, and a CSP block would surface as a failed request, not a successful empty response. Exam caveat: after adding outputs to the flow, rerun pa app add flow with the same flow ID so the generated types include them. Operational check: add the response action with the value as an output, regenerate the flow service, and confirm result.data carries the field.