killjoy
New Contributor III

Hi @Vidula Khanna​ , my solution was just rerunning the pipeline but I don't know in detail what was the issue. If it was internal with databricks maybe it was just a one-time thing, the error hasn't happened again since.