Skip to content

docs(session-replay): Document sticky V2 behavior when deleting last trigger group#17304

Open
inkeep[bot] wants to merge 1 commit into
masterfrom
docs-writer-ai-update-2026-06-04T20-47-40-136Z-g458f8
Open

docs(session-replay): Document sticky V2 behavior when deleting last trigger group#17304
inkeep[bot] wants to merge 1 commit into
masterfrom
docs-writer-ai-update-2026-06-04T20-47-40-136Z-g458f8

Conversation

@inkeep
Copy link
Copy Markdown
Contributor

@inkeep inkeep Bot commented Jun 4, 2026

Changes

This PR documents the new behavior when deleting the last trigger group in Session Replay settings, introduced in PostHog/posthog#61738.

What changed in the product

Previously, deleting the last trigger group would revert the project to legacy V1 recording settings. Now, deleting the last trigger group automatically replaces it with a default "Record all sessions" group (100% sampling, no conditions), keeping the project on V2 trigger groups.

Documentation update

Added a brief note in the "Trigger groups" section explaining:

  • What happens when you delete your last trigger group
  • That the project stays on V2 trigger groups rather than reverting to legacy settings

This PR was created by the Inkeep Content Writer agent, which is maintained by the Docs and Wizard team. Please reach out on Slack for help if needed.

…eting 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.
@inkeep inkeep Bot requested a review from ksvat June 4, 2026 20:48
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 4, 2026

Deploy preview

Status Details Updated (UTC)
🟢 Ready View preview Jun 04, 2026 09:01PM

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 4, 2026

Vale prose linter → found 10 errors, 16 warnings, 1 suggestions in your markdown

Full report → Copy the linter results into an LLM to batch-fix issues.

Linter being weird? Update the rules!

contents/docs/session-replay/how-to-control-which-sessions-you-record.mdx — 10 errors, 16 warnings, 1 suggestions
Line Severity Message Rule
18:54 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
20:54 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
22:54 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
24:54 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
30:142 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
30:246 warning Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. PostHogBase.ProductNames
30:308 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
71:4 warning 'With Event trigger conditions' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase
73:7 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
85:13 warning Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. PostHogBase.ProductNames
107:74 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
109:23 warning 'navigations' is a possible misspelling. PostHogBase.Spelling
111:9 warning Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. PostHogBase.ProductNames
132:1 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
132:13 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
133:1 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
134:1 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
135:1 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
144:142 error Use straight quotes and apostrophes, not curly ones. PostHogDocs.CurlyQuotes
144:177 error Use straight quotes and apostrophes, not curly ones. PostHogDocs.CurlyQuotes
158:125 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
176:154 warning Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. PostHogBase.ProductNames
194:77 warning Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. PostHogBase.ProductNames
203:107 warning Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. PostHogBase.ProductNames
216:12 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
266:24 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
275:87 warning 'navigations' is a possible misspelling. PostHogBase.Spelling

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 4, 2026

Hey @ksvat! This docs PR was generated for you by an agent. You're responsible for reviewing and merging it into production.

  1. Review and approve the PR
  2. Merge the PR
    a. Check the preview env and CI build and merge it yourself
    b. Enable auto-merge if you're confident in the changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants