Forum Discussion
Small model suddenly throwing Resource Governing errors on PowerBI.com
Involved Microsoft Premier Support and discovered the root cause - which wasn't what we thought it was. The business problem was that I had requisition approvals in Power Automate flows, but had a need to bring in data from both the source D365FO purchase requisitions and corresponding purchase orders; in addition, some data from vendors and employees to populate some of my view. As reqs are created throughout the day, I needed latest data - which I sourced from entities downloaded via ODATA connections.
I set the model to update on PowerBI.com every hour or so, so independent of the time it took to fish the data for the latest view, the current status on all reqs would be there whenever users dipped in to have a look.
There appears to have been a change in PowerBI.com where if a view takes longer than 225 seconds to source all its data, it will point blank refuse to show the view, citing that "lack of resources" error message - even if you pull up the display what was refreshed some time back.
Temporary fix is to add a slicer and set it with a start date just beyond the minimum date in the data set (in my case by 4 weeks in 18 months of data), then the visual will render. The long term fix is to shift the data sourcing to be via Azure Data Lake, so the query is several orders of magnitude faster than we can achieve with synchronous ODATA connections.
Involved Microsoft Premier Support and discovered the root cause - which wasn't what we thought it was. The business problem was that I had requisition approvals in Power Automate flows, but had a need to bring in data from both the source D365FO purchase requisitions and corresponding purchase orders; in addition, some data from vendors and employees to populate some of my view. As reqs are created throughout the day, I needed latest data - which I sourced from entities downloaded via ODATA connections.
I set the model to update on PowerBI.com every hour or so, so independent of the time it took to fish the data for the latest view, the current status on all reqs would be there whenever users dipped in to have a look.
There appears to have been a change in PowerBI.com where if a view takes longer than 225 seconds to source all its data, it will point blank refuse to show the view, citing that "lack of resources" error message - even if you pull up the display what was refreshed some time back.
Temporary fix is to add a slicer and set it with a start date just beyond the minimum date in the data set (in my case by 4 weeks in 18 months of data), then the visual will render. The long term fix is to shift the data sourcing to be via Azure Data Lake, so the query is several orders of magnitude faster than we can achieve with synchronous ODATA connections.