we are using the Reporting API with Power BI. In Power BI Service we have set up a refresh schedule. We have two issues with that and found a workaround only for one of the issues.
When the Query exceeds a certain timeframe (roughly 3 years), we always get an error 504 (Gateway Timeout).
I found a workaround, by splitting the query. We have a query for each year and append the tables to a single table.
Even with this workaround, we still have problems. Only a fraction of the refreshes are successful. Most refreshes still fail.
The error message is always the same: "OData: Request failed: The remote server returned an error: (500) Internal Server Error. Table: TimeTracker." ("TimeTracker" is the name of the query in our model.)
Not only is the data not up to date on most days. If the refresh fails too often in a row, Power BI Service automatically deactivates the refresh schedule and I have to activate it again manually.
I know it's load for your server. Unfortunately, Power BI Service does not allow to exclude a query from refresh (only works on Desktop).
On the other hand, we are not a huge company. We have around 35 employees creating ca. 40.000 rows/entries per year. I don't understand why you have such a strict limit and/or can't handle that load.
Is there anything we can do to mitigate the problem? For example, is there a way to exclude certain columns to reduce the load?
Please sign in to leave a comment.