Power Pages

Power Pages does not return Location header for flows with Asynchronous Response

(1) Share

Report

Posted on by salesmaster

Hi,

I am using Power automate with action 'When power pages calls a flow'.

Since it is a long-running flow, and often goes above the 2 min timeout threshold for portal API.

I saw there is a setting in the response which allows to send the response immediately and keep the flow running in the background like we have for HTTP triggered flows.

But unfortunately, the power pages API only returns the 202 status code and not the Location header to poll to.

It also returns the response like below -

{"ErrorCode":"0000000B","Message":"Default"}

Is there any way to handle long-running Power Automates like in HTTP triggers.

If there is a setting, that means there should be some way. Not sure what i am doing wrong.

Categories:

Power Apps portals

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

Valantis 6,286 on at

Like (1)

Report
Copy link

Link copied!

Hi @salesmaster,

The Power Pages cloud flow API wrapper (`/_api/cloudflow/v1.0/trigger/`) returns the 202 status code but does NOT pass through the Location header from the async response. The portal strips it, so you can't poll the flow's status URL directly from Power Pages.

The `{"ErrorCode":"0000000B","Message":"Default"}` response is the portal's error wrapper when the async response doesn't contain what it expects.

The workaround for long-running flows from Power Pages:
1. Fire-and-forget pattern: call the flow from Power Pages with no expected response. The flow runs in the background and writes its result to Dataverse when complete.

2. Status polling via Dataverse: in your flow, at key checkpoints, write status records to a Dataverse table (e.g. Status = 'Processing', then 'Complete'). On the Power Pages side, poll this Dataverse table via the portal API (`/_api/`) to check for the result. This is the confirmed workaround for async flows in Power Pages.

3. Reduce flow execution time: if possible, split the long-running work into smaller chunks or use async processing inside the flow to avoid the 2-minute timeout entirely.

There is no way to get the Location header from the Power Pages portal API the Dataverse status table pattern is the supported workaround.

Ref: https://learn.microsoft.com/en-us/power-pages/configure/cloud-flow-integration

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
Suggested answer

11manish 2,829 on at

Like (0)

Report
Copy link

Link copied!

The "When Power Pages calls a flow" trigger currently does not expose the Location header used by HTTP-triggered flows.

If your flow takes longer than the Power Pages request timeout, the recommended solution is to use a tracking record (Dataverse or SharePoint) and implement

status polling, rather than relying on the built-in HTTP asynchronous polling mechanism.

more reference :

https://sergeluca.wordpress.com/2018/02/01/pattern-for-making-long-async-http-calls-in-microsoft-flow/

https://learn.microsoft.com/en-us/power-automate/guidance/coding-guidelines/asychronous-flow-pattern

Was this reply helpful? Yes No