Forum Discussion
Aborting refresh if database is unavailable
Hi, is there a way to abort a refresh if the entire database on underlying dataset you are trying to access is unavailable or offline?
My data model has 2 major sources (both a PBI dataset that each pull from an internal database). The one underlying database can be down/unavailable at times. When my main model attempts daily refresh, (and the underlying database cannot be accessed), the data is wiped and nothing returned in my main model from that 1 source.
Is there a way to abort a refresh if the entire database you are trying to access is unavailable or offline? I would like to abort to retain what I pulled the previous refresh(the previous day in this case) instead of wiping out. A bonus would be that the 1 good dataset's refresh goes through and just the abort on the one that's temporarily unavailable so everything is as up-to-date as possible.
Hi KJBT
No you can't abort a refresh, though you can stop it before it kicks in if you were aware of the server availability.