Hi @CynAuad @sminamioka @learnawscloud @Kowsi
Thank you for your patience while we investigated this issue.
We flagged this to our teams internally, and the team has deployed a fix, and based on our checks, the behaviour should now be back to normal. This incident has affected a limited set of environments, which is why it was harder to reproduce internally and took longer to raise and resolve than we would have liked.
Please try again and let us know if you still see the problem. We are treating this as a priority, and any confirmation or remaining error details you can share will help us validate the fix and follow up quickly.
Thank you again for flagging this and for bearing with us.
If this answer resolves your question, could you mark it as โAccept as Solutionโ? That helps other users quickly find the correct fix.
Regards,
Ashwin | Delivery Solution Architect @ Databricks
Helping you build and scale the Data Intelligence Platform.
***Opinions are my own***