Good news. When I signed into Databricks this morning the issue seems to have gone away. All I did yesterday was sign out of databricks at the end of the workday and then sign in again this morning. So perhaps the issue was in Databricks for a subset of users and it has now been resolved.