fix(billing): Prevent crash on invalid data category for plan#112419
Closed
fix(billing): Prevent crash on invalid data category for plan#112419
Conversation
The getBucket function would throw an error when it couldn't find a valid bucket for a data category, causing the billing overview page to crash. Now it reports the error to Sentry with full context but returns a fallback bucket with zero price, allowing the page to continue rendering. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The billing overview page (
/settings/billing/overview/) was crashing when thegetBucketfunction encountered a data category that didn't have a corresponding bucket in the plan's configuration.This could happen when:
seer_user)Changes:
getBucketto report errors to Sentry with full context (buckets, events, price, shouldMinimize)Impact:
This maintains observability while providing a better user experience.