Forum Discussion

Priyamxylem's avatar
Priyamxylem
Helper I
5 months ago
Solved

Data Flow random refresh issue

For the past two months, I have been experiencing intermittent issues with the existing dataflow. At times, the refresh completes successfully, while at other times it fails with errors, even though ...
Need Help
  • rohit1991's avatar
    rohit1991
    5 months ago

    Hii Priyamxylem 

     

    Check gateway performance metrics, increase timeout if needed, review SQL server blocking/long-running queries, and stagger refresh schedules to avoid concurrency spikes. Also ensure the gateway and dataflow engine are on the latest version.

  • v-dineshya's avatar
    v-dineshya
    5 months ago

    Hi Priyamxylem ,

    Thank you for reaching out to the Microsoft Community Forum.

     

    Please try below things to fix the issue.

     

    1. Please share latest failed refresh error (ActivityId, RequestId, the pbi.error JSON).

    2. Run VNet “Troubleshoot network” to both your SQL host and the Fabric endpoints on TCP/1433 and share screenshots.

    3. Please confirm whether your dataflow uses referenced queries or writes to Lakehouse/Warehouse. If yes, validate that egress rule for 1433 is open from the VNet gateway subnet to Fabric.

    4. If you are using Dataflow Gen1 and using OAuth. try to move the logic to Dataflow Gen2 or a semantic model to avoid mid‑stream token expiry.

    5. Set up a Power Automate flow to retry once or twice on failure.

    6. Filter earlier, remove unused columns, avoid bmany-to-many merges; if you are using incremental logic, ensure filters fold to SQL.

     

    I hope this information helps. Please do let us know if you have any further queries.

     

    Regards,

    Dinesh

v-dineshya's avatar
v-dineshya
Community Support
5 months ago

Hi Priyamxylem ,

Thank you for reaching out to the Microsoft Community Forum.

 

Please try below things to fix the issue.

 

1. Please share latest failed refresh error (ActivityId, RequestId, the pbi.error JSON).

2. Run VNet “Troubleshoot network” to both your SQL host and the Fabric endpoints on TCP/1433 and share screenshots.

3. Please confirm whether your dataflow uses referenced queries or writes to Lakehouse/Warehouse. If yes, validate that egress rule for 1433 is open from the VNet gateway subnet to Fabric.

4. If you are using Dataflow Gen1 and using OAuth. try to move the logic to Dataflow Gen2 or a semantic model to avoid mid‑stream token expiry.

5. Set up a Power Automate flow to retry once or twice on failure.

6. Filter earlier, remove unused columns, avoid bmany-to-many merges; if you are using incremental logic, ensure filters fold to SQL.

 

I hope this information helps. Please do let us know if you have any further queries.

 

Regards,

Dinesh

v-dineshya's avatar
v-dineshya
Community Support
5 months ago

Hi Priyamxylem ,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.

 

Regards,

Dinesh

  • v-dineshya's avatar
    v-dineshya
    Community Support
    5 months ago

    Hi @Priyamxylem ,

    We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.

     

    Regards,

    Dinesh