I'm using powerBI to visualize data from kusto database.
I've defined a daily refresh (8 refreshs - due to limitaiton) and so far the refresh is working porperly every day (~15-20 min per refresh) but every week it seems like on Saturday the refersh is not working at all (constantly), even if I log in manually and do refresh now - it acts like it is working but no reflection of status done or failure in the UI history.
on Sudnay the schedule refresh kick back in and working fine even updating the history of Saturday to be completed fine.
anyone encountered something like this? is there anywhere I can get detail logs of the refresh attempts?
if any further informatino is needed I'll be happy to provide.
Solved! Go to Solution.
Thanks for your reply.
our application is constantly writting to kusto db so the data is there
and when doing the same query from the kusto explorer at that time it worked fine and returned results.
I also think I did the same query from Power BI desktop and it worked but I'll need to double check this the comming Saturday and get back to you on this (if it is fine?)
only from the power BI server it didn't work or at least didn't reflect the change both in the visualizations and the refresh history
can this be something in the communication between them? any way for me to look at detailed logs?
Of course when I checked this Saturday and it worked fine
so the general definition is working and I thnk I know what happen in the previous time.
it seems that I have one problimatic table that sometime based on the current time defined (1 week of data filter)
can generate 50K results and sometimes much much more, based on traffic and user actions.
and also the several times I got an email that the refresh failed was due to that table.
and the reason it works on the kusto explorer is maybe less stric settings.
is it possible to not cancel the entire dataset due to one table? or should I tweak the the filters