I see hopes for the ability to kill refreshes that run for an unusual length...I up voted that idea.
But any ideas on what causes this to happen? Lucky for us we have premium capacity which ups the timeout to 5 hours?? Hard to use in production with little or no control when who knows what is happening. The 5 hour timeout is not awesome either. Would be nice to have a timeout override per secheduled job...with a retry.
Nothing has changed on the Query and nothing substantial has changed with the data.
Tried turning off the gateway for a bit...then rebooted it for no good reason. The refreash keeps on truckin'. Now I am curious how long it will go...will it roll over after 100 hours?
So it does timeout after 24-hours. Support asked to capture gateway logs when it happens again...it is happening and there is nothing hitting the data. Nothing on the SQL server, nothing in the gateway. I saw someone asking about multi-factor...could that be an issue?