Subscription error on paginated report

[cw88]

Hi, 

i set up subscription on a paginated report. The report is based on a sematic model from a fabric warehouse. The subscription ran perfectly on a daily base for the last month. 

Yesterday i got the following error. Does anyone know whats the problem? Thanks!

There was an error with your subscription "Testsubscription" and it could not be delivered You are receiving this email because there was an error with a subscription to Paginated Report "Testsubscription" created by you.

Connection_Error_General There was an error communicating with Analysis Services. Please verify that the data source is available and your credentials are correct. The SQL pool is warming up. Please try again.. The exception was raised by the IDbConnection interface.

You can check the latest state of the report by clicking in the button below. Your next subscription is scheduled for August 22, 2024 18:00 UTC.

[Anonymous]

Hi, @cw88 

This can happen if your SQL pool has been inactive for a while and needs time to warm up before it can process requests. You can try to warm up the SQL pool by running a simple query or a light task before triggering the subscription. This helps ensure that SQL pool is ready to handle subscription requests. You can refer to the following link:

Azure Synapse SQL pool is warming up error - Microsoft Q&A

SQL Pool Warming Up: What It Is and How to Fix It (hatchjs.com)

How to Get Your Question Answered Quickly 

Best Regards

Yongkang Hua

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[cw88]

Hello @Anonymous ,

thanks for your reply, but i don't think that this is a good workaroud, because user can create subscriptions themselves, so times for the subscriptions can change every day. It is not possible to check every day when subscriptions run and schedule tasks before that...

[GilbertQ]

Hi @cw88 

What happens if you try and refresh the semantic model amount? Does it show something and then try and resend the subscription?

[cw88]

Hi @GilbertQ ,

resend of the subscription works. 

I had the same error "The SQL pool is warming up." at executing procedures on warehouse, for this case the solution was "configure a retry because it can happen that the warehouse needs some time until it is available". 

But for the subscriptions there is no option for retry...

[GilbertQ]

What I would do is try and create a pipeline to run a SQL query before the subscription runs and see if that works?