CompaniesLaunchDarklyIncidents
LaunchDarkly: Attribute target values changed from string to number type
Timeline of updates
- resolved
Beginning 15:10~ UTC, November 11th, we were made aware of an issue in the "Target users who match these rules" section in the feature flags Targeting tab within the LaunchDarkly UI. Impact: - New attribute target values were not changeable from str (string) to num (number) and vice versa (e.g. "500" <-> 500) - Existing attribute target values may have changed from str (string) to num (number) for affected customers Resolution: Our Engineering team were able to mitigate and resolve the issue at 16:10 UTC.
From LaunchDarkly’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.launchdarkly.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by LaunchDarkly, started 2020-11-11 15:10 UTC, resolved after 0 min, 1 update(s).
- Title
- Attribute target values changed from string to number type
- Vendor
- LaunchDarkly
- Date
- URL
- https://rewindex.com/company/launchdarkly/incidents/dg0s9brgmg1y
LaunchDarkly profileRecent LaunchDarkly incidentsAll outages on November 11, 2020LaunchDarkly in November 2020MarkdownJSON