06-26-2024 07:53 AM
Hi Databricks Community,
We faced a strange error today where the error below was returned when a notebook was being run. It only happens on git connected notebooks and on rerun it succeeds. What is the issue?
06-26-2024 01:58 PM - edited 06-26-2024 02:01 PM
I faced the same issue today. Very strange. Databricks didn't report any down time, but now I'm almost 100% sure there was.
Added a screenshot from my run today on single user job cluster.
07-01-2024 05:57 AM
Me and my team have also had the same issue, twice this month. Any update on the cause? We are reviewing reverting to using %run on notebooks to get around it...
07-01-2024 06:25 AM
FWIW, in case you are on Azure and West Europe, there was an incident last Wednesday for a couple of hours.
07-11-2024 02:47 AM
we are also facing this issue today for the second time within a span of 1 month. Please help !
07-11-2024 02:50 AM
There's another ongoing incident in West Europe, similar to the previous one:
Azure Databricks Status Page
07-11-2024 02:53 AM
There was an identical outage on June 26th. I encourage Databricks Team to honestly report this as an outage, not "degraded performance".
07-11-2024 02:54 AM
Same issue here since 9AM CEST.
07-11-2024 03:13 AM
Passionate about hosting events and connecting people? Help us grow a vibrant local community—sign up today to get started!
Sign Up Now