Our database usage has increased significantly over the past couple of weeks, and we have concerns that not addressing it soon could lead to a large outage. To avoid that, we are scaling up the database this morning.
This unfortunately means there will be a small blip as we cut over from the old instance, which could lead to failed reads/writes. Webhooks and background actions will retry – but expect your GraphQL API, frontend, and custom routes to fail on reads/writes.
