From a9c621e3e6d846e21837a423d87f2097a5aae1a3 Mon Sep 17 00:00:00 2001
From: "inkeep[bot]" <257615677+inkeep[bot]@users.noreply.github.com>
Date: Thu, 4 Jun 2026 20:48:24 +0000
Subject: [PATCH] docs(session-replay): document sticky trigger group behavior
 when deleting last group

When deleting the last trigger group, PostHog now replaces it with a
default "Record all sessions" group instead of reverting to legacy V1
recording settings. This reflects the frontend change in PR #61738.
---
 .../session-replay/how-to-control-which-sessions-you-record.mdx | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/contents/docs/session-replay/how-to-control-which-sessions-you-record.mdx b/contents/docs/session-replay/how-to-control-which-sessions-you-record.mdx
index d511578bfc70..9cd03166936d 100644
--- a/contents/docs/session-replay/how-to-control-which-sessions-you-record.mdx
+++ b/contents/docs/session-replay/how-to-control-which-sessions-you-record.mdx
@@ -187,6 +187,8 @@ For example, you could create:
 
 To create a trigger group, go to the [replay ingestion settings page](https://app.posthog.com/replay/settings#selectedSetting=replay-triggers) and click **Add** in the **Trigger groups** section.
 
+If you delete your last trigger group, PostHog automatically replaces it with a default "Record all sessions" group at 100% sampling with no conditions. This keeps your project on trigger groups rather than reverting to legacy recording settings.
+
 ### Migrating from legacy trigger settings
 
 If you have existing legacy trigger settings (URL triggers, event triggers, feature flags, sampling, and match type configured outside of trigger groups), you can automatically convert them to trigger groups.