Dataflow Gen2

[PBI_Admin12]

Hi Team,

I’m setting up a Power Automate flow to trigger a Dataflow refresh. This works fine for Dataflow Gen1, but for Gen2 in Power Automate I’m using the HTTP with pre‑authorized action as required.

The problem: Power Automate marks the run as failed, while Fabric shows the dataflow as successfully refreshed. Could you help explain why the flow is failing despite the refresh succeeding, and advise how to resolve this discrepancy?

[v-pnaroju-msft]

Hi PBI_Admin12,

We are following up to see if what we shared solved your issue. If you need more support, please reach out to the Microsoft Fabric community.

Thank you.

[v-pnaroju-msft]

Thankyou, @Vinodh247 for your response.

Hi PBI_Admin12,

We appreciate your inquiry through the Microsoft Fabric Community Forum.

We would like to inquire whether have you got the chance to check the solution provided by @Vinodh247 to resolve the issue. We hope the information provided helps to clear the query. Should you have any further queries, kindly feel free to contact the Microsoft Fabric community.

Thank you.

[Vinodh247 · Accepted solution]

Power Automate is failing due to response format, not due to refresh failure.

=======================

The refresh is actually succeeding. The failure is coming from power automate because dataflow gen2 does not return a clean 200 success response to the pre-authorized HTTP call. Instead, it returns an intermediate or empty response that Power Automate interprets as an error, even though Fabric completes the refresh in the background.

Reason why this happens?

• Gen2 refresh is asynchronous. The API triggers the job and exits without a proper success payload.
• Power Automate expects a standard 2xx response with a body, so it marks the action as failed.

How can you fix it?
• Wrap the HTTP action with “Configure run after” and treat failure as success if the Fabric refresh actually triggers.
• Or use the Fabric REST API for item refresh (preview) that returns proper status codes.
• Or add a follow-up GET call to poll the refresh history and decide success based on that instead of the initial trigger call.