Skip to content

The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.

[bot] sync troubleshooting guides to db (#43687)

Chris Chinchilla9dfc39d8f6d5
diff --git a/apps/docs/content/troubleshooting/how-to-bypass-cooldown-period.mdx b/apps/docs/content/troubleshooting/how-to-bypass-cooldown-period.mdx
index a67de5dfa99..fe3a95eca8a 100644
--- a/apps/docs/content/troubleshooting/how-to-bypass-cooldown-period.mdx
+++ b/apps/docs/content/troubleshooting/how-to-bypass-cooldown-period.mdx
@@ -1,10 +1,8 @@
---
-title = "How to bypass cooldown period"
-topics = [
-"platform"
-]
-keywords = ["cooldown", "disk resize"]
-database_id = "ab90c813-6152-4dad-86f7-937d799ca123"
+title = "How to bypass modification limits"
+topics = [ "platform" ]
+keywords = [ "modification limits", "disk resize" ]
+database_id = "6f6a34a6-ac3f-4fba-9c70-4f4b8c7aeda7"
---
This cooldown period isn't a Supabase limitation. It's rooted in how Amazon EBS (the underlying storage instance for our databases) manages volume modifications. After modifying a volume (e.g. increasing size, changing type, or IOPS), AWS enforces a mandatory 6-hour cooldown before allowing another modification on the same volume. This is to ensure data integrity and stability of the volume under load.