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

Message usage actual sent, suppressed or custom gateway should be counted separately #4480

Open
louischan-oursky opened this issue Jul 19, 2024 · 2 comments
Assignees
Labels
cooldown/enhancement minor enhancement that users can see

Comments

@louischan-oursky
Copy link
Collaborator

louischan-oursky commented Jul 19, 2024

Problem

Incorrect usage quota consumption when test mode is on

When test mode is on, and a SMS is sent to a phone number that should not receive SMS, and the should be counted separated and should not be billed.

Can this be used for billing?

image.png

Copy link

linear bot commented Jul 19, 2024

@fungc-io fungc-io changed the title Incorrect usage quota consumption when test mode is on Message usage should only count actual sent, ignore suppressed Jul 23, 2024
Copy link
Member

updated issue title

@fungc-io fungc-io added the cooldown/enhancement minor enhancement that users can see label Jul 23, 2024 — with Linear
@fungc-io fungc-io changed the title Message usage should only count actual sent, ignore suppressed Message usage should count actual sent, suppressed separately Aug 28, 2024
@fungc-io fungc-io changed the title Message usage should count actual sent, suppressed separately Message usage actual sent, suppressed should be counted separately Aug 28, 2024
@fungc-io fungc-io changed the title Message usage actual sent, suppressed should be counted separately Message usage actual sent, suppressed or custom gateway should be counted separately Sep 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cooldown/enhancement minor enhancement that users can see
Projects
None yet
Development

No branches or pull requests

2 participants