feat(billing): use Subscription.orgRetention in customerOverview #103124
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| {customer.dataRetention || '90d'} | ||
| {customer.orgRetention?.standard | ||
| ? `${customer.orgRetention?.standard}d` | ||
| : '90d'} |
Member
There was a problem hiding this comment.
what's the reason we fallback to 90d?
Contributor
Author
There was a problem hiding this comment.
Good catch. This is actually an existing bug, because we show 90-day retention for free orgs.
It should fall back to the errors retention for the org (all plans have DataCategory.ERROR), and then perhaps fall back to 90.
isabellaenriquez
approved these changes
Nov 24, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is stack on top of #103118 and is a follow up to https://github.com/getsentry/getsentry/pull/18799