Davide
New Contributor II

Hello everyone, 

After following up with Databricks, they recognize it is a bug on their side therefore are starting the process to fix it, in the mean time the best way to deal with it according to Databricks is simply to setup a retry and it should work

 

Thanks for anyone who helped

View solution in original post