# Supabase: Management API Postgres config updates overwriting previous updates

> Supabase reported that Postgres config changes through the Management API only saved the latest values and overwrote earlier changes. Supabase identified the cause, deployed a fix, and disabled some dashboard config changes during the incident. The incident is resolved and lasted 2 hours and 8 minutes.

- Provider: [Supabase](https://outages.cc/supabase.md)
- Type: Incident
- State: Resolved
- Worst impact: Operational
- Started: 2026-11-03 04:56 UTC
- Resolved: 2026-11-03 07:04 UTC (lasted 2 h 8 min)
- Official update: https://status.supabase.com

## Updates from Supabase

### resolved, 2026-11-03 07:04 UTC

Connection Logging feature is working fine for all customers now.

### monitoring, 2026-11-03 06:27 UTC

A fix has been deployed, and the Connection Logging setting that was temporarily disabled on the dashboard is available again.

### monitoring, 2026-11-03 06:21 UTC

We have identified the cause and are deploying a fix. The dashboard setting that was temporarily disabled will soon be enabled again.

### investigating, 2026-11-03 05:18 UTC

We are actively correcting an issue with the Management API: • Postgres Config changes only save the latest values sent. Past changes are being overwritten For now, we have disabled making certain Postgres config changes on the dashboard until the issue is resolved.

### investigating, 2026-11-03 04:57 UTC

We are actively correcting an issue with the Management API: • Postgres Config changes only save the latest values sent, past changes are not being saved For now please refrain from not making any Postgres Config changes via the [Management API](https://supabase.com/docs/reference/api/introduction) or in the [Database Settings Dashboard](https://supabase.com/dashboard/project/\_/database/settings)