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.

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

Resolving Account Payment Issues #271

Closed
ghengeveld opened this issue Mar 22, 2024 · 5 comments · Fixed by #282
Closed

Resolving Account Payment Issues #271

ghengeveld opened this issue Mar 22, 2024 · 5 comments · Fixed by #282
Assignees
Labels
bug Classification: Something isn't working sev:S2

Comments

@ghengeveld
Copy link
Member

ghengeveld commented Mar 22, 2024

From AP-4349

What

We have two flags, Account.exceededThreshold and Account.paymentRequired that need to be handled in the addon.

Why

The user may be blocked from running builds successfully in the Addon and they would not know this until they aim to run a build.

@ghengeveld ghengeveld added the feature Classification: New feature label Mar 22, 2024
@MichaelArestad
Copy link
Contributor

I do not remember if these were implemented, but we have designs to alert folks when the free limit is exceeded. We should do a similar pattern for the above issues.

image

@shilman shilman added bug Classification: Something isn't working and removed feature Classification: New feature labels Mar 28, 2024
@ghengeveld ghengeveld self-assigned this Apr 1, 2024
@ghengeveld
Copy link
Member Author

FWIW we already have this screen for when the build you just ran was limited. We just don't show this screen "preemptively", before running a build. We need a Chromatic API update to support that.

@shilman
Copy link
Member

shilman commented Apr 2, 2024

@ghengeveld If that's the case we can probably move this to nice-to-have. @MichaelArestad Can you please confirm?

@MichaelArestad
Copy link
Contributor

This will impact all newer users to Chromatic who hit the limit. We do have emails that go out IIRC so this can probably be a nice-to-have. I don't know what percentage of users actually hit the limit. CC @ethriel3695

@ethriel3695
Copy link

@MichaelArestad @shilman @ghengeveld
People hit the free tier limit quite frequently. It's not too big of a deal, though, because they know they don't get more snapshots or builds until the next billing cycle or unless they update to a self-serve plan.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Classification: Something isn't working sev:S2
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants