https://approjects-vendor-status-watch.static.hf.space/v/flagsmith.htmlIncidents from Flagsmith's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://stspg.io/8m3kd4zy10syflagsmith:2026-09-10T14:43:49.808ZThu, 10 Sep 2026 14:43:49 +0000This incident has been resolved.https://stspg.io/z3yyd7bjvr8wflagsmith:2026-03-03T17:00:00.000ZTue, 03 Mar 2026 17:00:00 +0000### What Happened On Monday 3rd March at around 17:00 UTC, we deployed a release to the Edge API that inadvertently changed the JSON types returned for integer-typed feature state values. Values that had previously been returned as JSON strings \(e.g., `"300"`\) began returning as JSON numbers \(e.g., `300`\). The change affected the `/api/v1/environment-document/` endpoint used by SDKs operating in local evaluation mode. Features stored as strings, booleans, or null values were not affected, and the Core API was not affected. Our existing test suite did not catch the type change before it reached production. The issue was reported at 18:12 UTC, classified as P0 at 18:27 UTC, and we completed a rollback to the previous stable release by 18:36 UTC, restoring the expected behaviour. ### Whttps://stspg.io/kbcrbv0kz1rxflagsmith:2026-01-22T16:56:10.711ZThu, 22 Jan 2026 16:56:10 +0000This incident has been resolved.https://stspg.io/tqxsztd9f4hnflagsmith:2025-10-23T10:08:08.000ZThu, 23 Oct 2025 10:08:08 +0000All issues with the asynchronous task processor have been resolved and all operations in the Flagsmith UI are working as expected.