- Level
- confirmed
- Worst impact
- Major outage
- Components
- Admin API
- Down Index
- 44of 100
What to do
Check whether you use Flagsmith Admin API. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2023-09-05 12:01 UTC and 2023-09-05 12:01 UTC may need a replay.Subscribe to Flagsmith's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=flagsmith works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Flagsmith 6
- investigating
We are currently investigating this issue.
provider
- identified
We have identified a database migration that has failed as part of a new release. We are working to re-apply the migration.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- resolved
This incident has been resolved. A postmortem will follow.
provider
- postmortem
**Summary** On September 5th at 09:45 UTC, we initiated a release that included a database migration aimed at introducing a new constraint to the table containing information related to flags. According to our pre-live tests, this task should not have taken more than 50 milliseconds. Unfortunately, during the release to production, due to the high throughput on a particular table that it needed to acquire a temporary lock on, this caused a backlog of blocked connections waiting on the migration to complete. This caused a knock on effect that exhausted the connections on the database and a full restart was necessary. Once the restart was complete, the connections were restored and service was resumed. This happened at 10:20 UTC. **Next Steps** We have researched the cause of the issue and we do still have further research to understand certain aspects. Our current plan in the meantime is to implement certain safeguards as can be found in the following links to the Postgres documentation which should help reduce any impact in the future. [https://www.postgresql.org/docs/11/runtime-config-client.html](https://www.postgresql.org/docs/11/runtime-config-client.html) [https://www.postgresql.org/docs/11/runtime-config-logging.html](https://www.postgresql.org/docs/11/runtime-config-logging.html) \(`log_lock_waits`\)
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-04c20c2663
Is Flagsmith still down?
No, this incident was resolved 2023-09-05 12:01 UTC. For Flagsmith's live state, see https://down.guide/flagsmith.
How long did it last?
0m, from 2023-09-05 12:01 UTC to 2023-09-05 12:01 UTC, by the times Flagsmith posted.
What was affected?
Flagsmith named Admin API.
What caused it?
Flagsmith hasn't published a root cause. If it does, it shows here.
Where does this come from?
Flagsmith's official status page, https://status.flagsmith.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.