Fabric Warehouse - This query was rejected due to current capacity constraints.

[abm_chris]

Hi, I've had this issue on a particular report from around two weeks ago it was reported when I get:

'This query was rejected due to current capacity constraints.'

I know the report has worked previously otherwise I wouldn't have published it, even when returning 2500 rows/16 columns I am getting the same issue on an F64 capacity, there's nothing else struggling on the capacity so really confused with the error. I have had this ticket raised for two weeks now with Microsoft and currently on my third support engineer with no sign of progress and suggestions such as run less parameters or split the data into different reports are not ideal and hardly user friendly for those that rely on the reports. I want to use the Data Warehouse in Fabric product if possible but I feel I may have to go back to Azure SQL Server if it can't handle this amount. 

Has anyone else encountered the 'This query was rejected due to current capacity constraints.' error before and had any success with fixing it?

[v-cboorla-msft]

Hi @abm_chris 

Thanks for using Microsoft Fabric Community.

Apologies for the inconvenience.

Typically, a complex query running in a workspace assigned to a small capacity SKU size should run to completion. However, if the data retrieval or intermediate data processing physically can't run within the burstable scale factor, it results in the following error message: This query was rejected due to current capacity constraints. Review the performance guidelines to ensure data and query optimization prior to increasing SKU size. To increase the SKU size, contact your capacity administrator.

For details please refer : Considerations.

I understand that clearing cookies and caches might be helpful in troubleshooting the issue you're encountering.

Temporary Glitch: Clearing cookies and caches can sometimes resolve temporary glitches within the application that might be causing the error. 

Corrupted Data: In rare cases, corrupted data stored in the browser's cache related to Microsoft Fabric might be causing the issue. Clearing the cache removes this potentially problematic data.

If you have raised the support ticket, a reference to the ticket number would be greatly appreciated. This will allow us to track the progress of your request.

If the issue still persists, please do let us know. Glad to help.

Hope this information helps.

Thanks

[v-cboorla-msft]

Hi @abm_chris 

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.
In case if you have any resolution please do share that same with the community as it can be helpful to others.
Otherwise, will respond back with the more details and we will try to help.

Thanks.

[abm_chris]

No haven't reached a solution yet, looked at lowering one of the varchar column sizes. Query worked and has since reverted and getting the same issue again.

[v-cboorla-msft]

Hi @abm_chris 

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others.
If you have any question relating to the current thread, please do let us know and we will try out best to help you.
In case if you have any other question on a different issue, we request you to open a new thread.

Thanks.