We've rolled back a change which has resolved this issue. Thanks for bearing with us.
This issue was caused by a minor Notion incident (see status.notion.so) which prevented Granola from creating databases. It's now resolved and the behaviour is back to normal.