Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Error: Request getNotifications failed with message: /usage.v1.BillingService/GetUpcomingInvoice INTERNAL: failed to find customer #13058

Closed
jldec opened this issue Sep 18, 2022 · 1 comment
Closed

Error: Request getNotifications failed with message: /usage.v1.BillingService/GetUpcomingInvoice INTERNAL: failed to find customer #13058

jldec opened this issue Sep 18, 2022 · 1 comment
Assignees
@svenefftinge
Labels
team: webapp Issue belongs to the WebApp team type: bug Something isn't working

Comments

@jldec
Copy link
Contributor

jldec commented Sep 18, 2022

Noticed this error in the dashboard (browser developer console) on gitpod.io while doing UBP walkthrough (internal) with a new team. (admin). That team has been configured with usage-based billing.

The same error appears for all members of the new team, and no usage-limit exceeded notifications are shown.
Screenshot 2022-09-19 at 00 52 17
@jldec jldec added type: bug Something isn't working team: webapp Issue belongs to the WebApp team labels Sep 18, 2022
@jldec jldec moved this to Scheduled in 🍎 WebApp Team Sep 18, 2022
@jldec jldec mentioned this issue Sep 18, 2022
Closed
@svenefftinge svenefftinge self-assigned this Sep 19, 2022
@svenefftinge
Copy link
Member

This is outdated as the corresponding code was changed with #13016

Repository owner moved this from Scheduled to Done in 🍎 WebApp Team Sep 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@svenefftinge svenefftinge

Labels
team: webapp Issue belongs to the WebApp team type: bug Something isn't working
Projects
🍎 WebApp Team
Status: Done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@svenefftinge @jldec