Hi all.
I have a WF scheduled to run at night. It takes data from a serverless SQL pool which is down after a certain time of inactivity and wakes up "on demand" once it is called (usually it takes 1 min to wake up).
What is happening is that the scheduled WF sometimes fails with error "...the SQL pool is warming up", it will then wake up in a small amount of time and requires a second manual run in order to work properly.
The workaround I am currently using is to have a second WF scheduled 5 mins before the other to eventually wake up the pool and allow the main one to run properly, but I am looking for a more elegant solution, ideally without the need of a second dummy WF.
Do you have a nicer solution for this kind of scenario? Thank you in advance
