Query resources Exceeded error

[EdenStart11_20]

I’m working on publishing a Power BI report that includes a table visual with multiple columns sourced from different tables and data sources such as dataflows, APIs, and direct tables. The visual works perfectly in Power BI Desktop, but once I publish it to the service, I encounter an error stating that query resources exceeded the time limit—even when I limit the dataset to just 1,000 records.

The issue seems to be tied to one specific column from the API data source. If I remove that column, the report runs fine without any errors.But, I need that column included in the visual, and its presence consistently causes the timeout problem.

[v-priyankata]

Hi @EdenStart11_20 

Thank you for reaching out to the Microsoft Fabric Forum Community.

@lcorbet @ibarrau @GilbertQ Thanks for the inputs.

I hope the information provided by users was helpful. If you still have questions, please don't hesitate to reach out to the community.

[GilbertQ]

Hi @lcorbet 

There sometimes can be underlying issues with the Power BI  service which typically get resolved within a few hours. I would recommend trying to test it again tomorrow morning to see if your issue gets resolved. With regards to your error. I would highly recommend looking at the column cardinality and using something like DAX Studio in order to understand which columns are taking up the most memory in your semantic model. And your options are if it is taking a lot of memory, either to remove it as recommended or increase capacity size, or look at different ways to represent the same kind of data.

[lcorbet]

We had a Power BI Service user report this error yesterday afternoon on a report that has never had a problem with resources. This morning, the system is rendering very slowly. Is something going on more broadly?

[ibarrau]

Hi. If it's just columns and it's mandatory the way the table looks. It sounds like you need to reconsider or redesign your data model considering this requirement. That's why it's so important to take the time to build a good start schema with the data. That would prevent this issues. If it's not a column but measure, then reconsider optimizing the code. Read about some ways to optimize engines with SQLBI blogs/videos.

I hope that helps,