I encountered the same issue after switching from Databricks Community Edition to Databricks Free Edition. After I detach and reattach the serverless compute, however, the problem went away, likely due to the legacy notebook settings.