---
name: LaunchDarkly Changelog
slug: launchdarkly-changelog
type: scrape
source_url: https://launchdarkly.com/changelog/
organization: LaunchDarkly
organization_slug: launchdarkly
total_releases: 5
latest_version: April 2026
latest_date: 2026-04-06
last_updated: 2026-04-16
tracking_since: 2026-03-09
canonical: https://releases.sh/launchdarkly/launchdarkly-changelog
organization_url: https://releases.sh/launchdarkly
---

<Summary type="rolling" window-days="90" release-count="5">
LaunchDarkly shifted focus toward operational resilience and observability integration. The platform now prevents event loss during authentication failures by automatically buffering SDK events to S3 with automatic replay once services recover, ensuring no telemetry gaps during outages. On the experimentation side, Guarded Releases moved to absolute difference measurements and removed manual metric thresholds, reducing false positives and stabilizing charts earlier in test runs. Flag management also gained workflow-friendly capabilities: operators can now restore previous targeting configurations directly from change history as drafts, respecting approvals and scheduled changes, while observability expanded to include Datadog Agent ingestion alongside OpenTelemetry, and user feedback notifications landed in Slack with sentiment signals and variation context.
</Summary>

<Summary type="monthly" period="March 2026" release-count="4">
Infrastructure and experimentation matured this month. Resilient Event Ingestion now buffers SDK events to S3 during authentication outages, preventing data loss with automatic failover and replay once services recover. Guarded Releases shifted to absolute difference measurement and eliminated manual metric thresholds, reducing false positives and improving chart stability early in experiments. Beyond core features, Datadog Agent ingestion opened observability data collection to non-OpenTelemetry customers, and User Feedback notifications graduated to Slack, letting teams triage submissions with sentiment and flag variation context directly in their messaging workspace.
</Summary>

<Release version="April 2026" date="April 6, 2026" published="2026-04-06T00:00:00.000Z" url="https://launchdarkly.com/changelog/#april-2026">
## Restore Previous Flag Version

You can now restore a previous targeting configuration for a flag directly from Change history. Load a recent targeting update into the flag editor as a draft, review and edit it in the targeting UI, then save to update the current configuration. Rollback respects existing workflows including comments, approvals, and scheduled changes, and is scoped to recent targeting-only versions for safe application.
</Release>

<Release date="March 20, 2026" published="2026-03-20T00:00:00.000Z" url="https://launchdarkly.com/changelog/#resilient-event-ingestion">
## Resilient Event Ingestion

Resilient Event Ingestion prevents permanent data loss during authentication outages by automatically writing raw SDK events to S3 instead of dropping them when LaunchDarkly's authentication dependencies become unavailable. Features automatic failover (requests that would return 5xx errors are stored in S3 with 202 acknowledgment) and data replay once authentication is recovered. This is an infrastructure-level improvement available to all customers across all regions with no action required.
</Release>

<Release date="March 13, 2026" published="2026-03-13T00:00:00.000Z" url="https://launchdarkly.com/changelog/#absolute-difference-with-no-metric-thresholds">
## Absolute difference with no metric thresholds

Guarded releases now use absolute difference (not relative difference) when measuring regressions and displaying charts. With the improved stats approach and reduced false positives, manual metric thresholds are no longer required and have been removed from configuration. Charts show improved stability without wide variability during early stages.
</Release>

<Release date="March 11, 2026" published="2026-03-11T00:00:00.000Z" url="https://launchdarkly.com/changelog/#datadog-agent-ingestion">
## Datadog Agent ingestion

Datadog customers not using OpenTelemetry can now send observability data to power Guarded Releases, Experiments, and other features.
</Release>

<Release date="March 9, 2026" published="2026-03-09T00:00:00.000Z" url="https://launchdarkly.com/changelog/#slack-notifications-for-user-feedback-are-now-live">
## Slack notifications for User Feedback are now live

You can now route **user feedback** directly to Slack using the LaunchDarkly Slack bot. When a user submits feedback on a feature flag, your team gets a real-time notification in the Slack channel where they already work complete with sentiment signals, feedback content, and the exact flag variation the user saw.

**What's new:**
* Route feedback to any Slack channel your team uses
* See sentiment, feedback content, and flag variation context right in the notification
* Set it up in seconds from the Feedback tab on any feature flag
</Release>