[Bug] Local Code Apps player fails to load after adding Flow

[ranjith7022]

Summary

In a Code Apps project created from the starter template, the local player fails to load the app after adding a Flow. This reproduces even when the flow is a manual-trigger flow and its generated model/service files are created correctly.

The failure appears to happen during DLP evaluation for the app in local play mode.

Environment

• Template: https://github.com/microsoft/PowerAppsCodeApps/tree/main/templates/starter
• @microsoft/power-apps: 1.1.1
• @microsoft/power-apps-vite: 1.0.2
• Power Apps CLI: 0.10.0
• Repro observed in local development

Steps to reproduce

1. Create a new app from the starter template.
2. Add a Logic Flow using the latest Power Apps CLI flow-add capability.
3. Confirm the flow is added under connectionReferences in power.config.json.
4. Start local development.
5. Open the app in the local player.

Expected behavior

The app should load successfully in the local player after adding the flow.

Actual behavior

The app fails to load in the local player when the Logic Flow reference is present.

Console/network errors

.../powerapps/evaluateDlpPoliciesForApp?api-version=1
Failed to load resource: the server responded with a status of 500 ()

Uncaught (in promise) {
  code: "AppLoadFailed",
  errorType: "PlatformError",
  message: "Cannot read properties of undefined (reading 'evaluationResult')",
  source: "app-host",
  sourceScenarioName: "PlayerLifecycle.PlayerSDK.PlayApp.CheckDataLossPolicyForApp"
}

### Additional detail

For a scheduled flow, code generation produces a service that imports a model file that is never generated. For example, the generated service contains:

```ts
import type { ManualTriggerInput } from '../models/FlowNameModel';

[ranjith7022]

I added the flow using the Power Apps CLI command below:

npx power-apps add-flow --flow-id 00000000-0000-0000-0000-000000000000

[eschavez]

Thanks for filing this with the detailed repro steps. We're able to reproduce the failure you're describing — when a Logic Flow is added to a Code App, the local player hits a 500 from the DLP policy evaluation endpoint, causing the app to fail to load.

The CLI now has support for adding flows; however, there are dependent player-side changes that need to finish deployment before an app with flow connection references can be played in local mode. We expect this to resolve once that rollout completes.

In the meantime, could you check if publishing the app works for you? Publish goes through a different path and may not be affected by the local player dependency.

We'll share updates here as we make progress.

[ranjith7022]

Thanks for the update. I confirmed that pushing the app is working now.

I also found another issue on the code generation side. For example, for a scheduled flow for example "Sample Scheduler Flow", if the flow has no input parameters and no output parameters, the CLI does not generate a model file. However, the generated service still imports ManualTriggerInput from that missing model file, which leaves the generated code referencing a type that does not exist.

When I tried this in my environment:

• A flow with the trigger "When Power Apps calls a flow (V2)" is working.
• A flow with the trigger "Manually trigger a flow" still throws this error:

Retrieve operation failure: Failed to acquire access token: [{"errorName":"Core.ApplicationError","serializedVersion":0,"message":"Unable to find api with id AppMagic.Services.ServiceError"}]

Thanks for adding flow support — this is already very useful.

[eschavez]

Thanks for the additional details — this is helpful context.

The Unable to find api with id AppMagic.Services.ServiceError error for "Manually trigger a flow" is expected for now. Code Apps currently only supports flows with the "When Power Apps calls a flow (V2)" trigger type — the same constraint that applies to canvas apps. Flows with other trigger types (including "Manually trigger a flow" and scheduled flows) are not yet supported for invocation from a Code App.

We recognize that the CLI currently doesn't prevent you from adding unsupported flow types, which leads to the broken generated code and runtime errors you're seeing. We're planning a fix to validate the trigger type during add-flow and surface a clear error instead of silently adding an unsupported flow.

For now, please use flows with the "When Power Apps calls a flow (V2)" trigger — those should work end-to-end. We'll update this issue once the validation fix is in place.