Forum Discussion
Issues with Automated Refreshes on PBI Server - But Works Fine In The App
Hi mjkusler,
Even after trying various approaches, If you are still unable to solve the issue you can reach out to Support by raising a ticket with Microsoft Support.
Please refer below link on how to raise a contact support or support ticket.
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Hammad.
Community Support TeamIf this post helps then please mark it as a solution, so that other members find it more quickly.
Thank you.
Hi mjkusler
Your issue likely stems from a timing conflict between Databricks' table update process and Power BI's scheduled refresh. The failure occurs at the same time daily, suggesting that Power BI is querying the table while it's being updated or temporarily unavailable. The error message indicates missing columns, but the specific column varies, implying an inconsistent schema during refresh. Since manual refresh works fine, the table is likely restored after the scheduled refresh fails. Other tables follow the same pipeline but don’t fail, meaning this specific table might have a slower or more complex update process. The S3 to Databricks transfer should be checked for delays, locks, or incomplete data loads at the failure time. Databricks’ metadata caching could also cause Power BI to see an outdated schema. Solutions include adjusting the refresh schedule, ensuring table availability before refresh, or using a staging table to maintain consistency. Adding logging in Databricks can help track when the table is fully updated before Power BI queries it.
Poojara_D12 @ I appreicate the response. However, this has all been explored and tested including various different settings, configuartions, code changes, refreshing schedules changes etc. Still no luck