I recently started using PowerAutomate to trigger some refreshes within PowerBI and noticed that when something fails to refresh, it often has an activity ID with all zeros. Admittedly, I'm not 100% sure if this specific to a failed refresh triggered from PowerAutomate, or just a routine thing. When I look at failed refreshes from the past before I started using PowerAutomate, they seem to have an Activity ID even with a similarly-failed-connection as the reason.
For reference, here is a recent example:
| Failed Connections: | Query - ActualTarget |
| Cluster URI: | WABI-US-NORTH-CENTRAL-redirect.analysis.windows.net |
| Activity ID: | 00000000-0000-0000-0000-000000000000 |
| Request ID: | 0c45d802-2ff9-48d1-a2db-f1305ab5acb4 |
| Time: | 2020-06-07 21:37:34Z |
I am trying to find out where to diagnose - if this is related more to PowerAutomate, or possibly hitting some kind of limit on refreshes? or even some kind of strain on the server?
This has happened often in the last few days, with all of my tests, on items that typically have no issue refreshing. When I trigger an on-demand refresh or scheduled refresh within PowerBI, it seems to fail far less often than ever over the last 2 days of tests. The refresh clearly begins to start - and sometimes works - but other times, it fails and gives the above type of reasoning.
Any help would be much appreciated!
