[Billing] Add changelog for default-on Budget alerts#31467
[Billing] Add changelog for default-on Budget alerts#31467ryan-noel-2258 wants to merge 8 commits into
Conversation
Review⏸️ Automatic reviews for this PR are paused. This PR has already received 2 automatic reviews. To run another review, a codeowner can comment
✅ No style-guide issues found in full PR diff. CommandsOnly codeowners can run commands. Post a comment with the command to trigger it.
|
|
ryan-noel-2258
changed the title
|
/full-review |
|
|
||
| We are turning on Budget alerts by default for eligible Pay-as-you-go accounts. If your account does not already have a budget alert, Cloudflare will create one for you with a $10 account-level threshold. Your default alert will enable at the turn of your next billing cycle, so it will not fire based on usage you have already incurred. | ||
|
|
||
| The default alert behaves exactly like an alert you would create yourself. When your cumulative usage-based spend this cycle reaches the threshold, you receive an email notification. The alert is informational only. It does not cap your usage or impact your account in any way. |
There was a problem hiding this comment.
Who on the account gets an email notification?
There was a problem hiding this comment.
this goes to the primary email on file; same as where the invoice is delivered
|
/bonk review PR |
| date: 2026-06-15 | ||
| --- | ||
|
|
||
| We are turning on Budget alerts by default for eligible Pay-as-you-go accounts. If your account does not already have a budget alert, Cloudflare will create one for you with a $10 account-level threshold. Your default alert will enable at the turn of your next billing cycle, so it will not fire based on usage you have already incurred. |
There was a problem hiding this comment.
Your default alert will enable at the turn of your next billing cycle, so it will not fire based on usage you have already incurred.
Why this caveat?
There was a problem hiding this comment.
Think I answered this in Gchat somewhere, but confirming. We don't want mid cycle alerts firing to create noise upon creation due mostly due to sensitivity around escalations and tickets. Just being safe.
|
|
||
| We are turning on Budget alerts by default for eligible Pay-as-you-go accounts. If your account does not already have a budget alert, Cloudflare will create one for you with a $10 account-level threshold. Your default alert will enable at the turn of your next billing cycle, so it will not fire based on usage you have already incurred. | ||
|
|
||
| The default alert behaves exactly like an alert you would create yourself. When your cumulative usage-based spend this cycle reaches the threshold, you receive an email notification. The alert is informational only. It does not cap your usage or impact your account in any way. |
There was a problem hiding this comment.
Should mention alerting delay so users aren't confused why their alert has not triggered?
There was a problem hiding this comment.
updated. thank you
|
@ryan-noel-2258 has this shipped? |
|
@vy-ton no, we are shipping this incrementally based off user billing cycle anchor dates. So at the turn of the billing cycle, the default alerts are created. Hoping to get started this week. |
|
Hey there, we've marked this pull request as stale because there's no recent activity on it. This label helps us identify PRs that might need updates (or to be closed out by our team if no longer relevant). |
3 participants
Summary
Adds a new changelog entry announcing that PAYGO Budget alerts are now enabled by default for eligible Pay-as-you-go accounts.
What changed
src/content/changelog/fundamentals/2026-06-15-budget-alerts-default-on.mdxContext
Follow-on release to the April 2026 Budget alerts GA. Cloudflare now automatically creates a $10 account-level budget alert policy for every eligible Pay-as-you-go account that does not already have one. Each account's default policy activates on the first day of its next billing cycle, so the customer-visible rollout naturally spreads across a billing cycle.
Customers can edit the threshold, add more alerts, or delete the default alert from the same dashboard surfaces as a user-created alert. Existing user-set policies are not modified.
Validation
astro check: 0 errors, 0 warnings on changed fileReview
Per the Contributing to the changelog process, will post to the Changelog reviews chat for PM review after this PR is open.