Skip to content

:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.

chore(workflows): drop the hourly cap from email sending tiers (#129137)

Meikel Ratzf6e369f6b36e
diff --git a/docs/internal/workflows-email-sending-tiers.md b/docs/internal/workflows-email-sending-tiers.md
index bf9c3d7915cc..a65339a16c47 100644
--- a/docs/internal/workflows-email-sending-tiers.md
+++ b/docs/internal/workflows-email-sending-tiers.md
@@ -1,6 +1,6 @@
# Workflow email sending tiers
-Every project has a trust tier that caps how much workflow email it can send: an hourly cap, a daily cap, and a maximum batch audience.
+Every project has a trust tier that caps how much workflow email it can send: a daily cap and a maximum batch audience.
Projects start at the lowest tier and earn higher ones by sending cleanly; dirty rates, AWS tenant reputation findings, suspensions, and long dormancy move them down.
The tiers exist because all workflow email shares one SES account whose reputation pools every project's complaints.
Only workflows that send email are subject to the tiers; SMS, push, and webhook activity is never capped by them.
@@ -11,7 +11,7 @@ Transactional email is never delayed by the send-time caps, but it is still char
- Tier state: `email_sending_tier`, `email_sending_tier_updated_at` (dwell anchor), `email_sending_tier_demoted_at` (demotion cooldown anchor), and `email_sending_tier_pinned` on `TeamWorkflowsConfig`.
- Tier movement: a daily Celery sweep (07:15 UTC, after the SES tenant-state reconcile at 07:00) in `products/workflows/backend/services/email_sending_tier.py`.
- Batch audience cap: `get_hogflow_batch_trigger_limit` in `products/workflows/backend/utils/batch_trigger_limit.py`, applied at batch dispatch and shown in the blast radius preview.
-- Send-time caps: two Valkey token buckets per team in the CDP email worker (`claimTeamSendingBudget` in `nodejs/src/cdp/services/messaging/email.service.ts`).
+- Send-time cap: one Valkey token bucket per team in the CDP email worker (`claimTeamSendingBudget` in `nodejs/src/cdp/services/messaging/email.service.ts`).
- Staff controls: the team's Django admin page (view state, set/pin a tier, recompute now).
- Audit trail: every tier or pin change writes an `email_sending_tier_changed` row to the team's activity log, with the before and after values and the decision reason (`staff_set` for a tier staff set by hand). Staff rows name the acting user. Sweep and backfill rows carry a trigger with the job type and a per-run id. The rows are staff-only in the activity log (`products/workflows/backend/services/email_sending_tier_audit.py`).
- Customer surface: the Reputation tab's sending allowance card, shown only while the team is enforced.
@@ -31,7 +31,7 @@ Set them together; drift means the UI describes limits the worker does not apply
Django (`posthog/settings/web.py`):
- `WORKFLOWS_EMAIL_TIER_MODE`: `off` (default), `shadow`, or `enforce`. Unrecognized values read as `off`.
-- `WORKFLOWS_EMAIL_TIER_HOURLY_CAPS`, `WORKFLOWS_EMAIL_TIER_DAILY_CAPS`, `WORKFLOWS_EMAIL_TIER_BATCH_AUDIENCE_CAPS`: comma-separated tables indexed by tier. The shortest table decides the tier count.
+- `WORKFLOWS_EMAIL_TIER_DAILY_CAPS`, `WORKFLOWS_EMAIL_TIER_BATCH_AUDIENCE_CAPS`: comma-separated tables indexed by tier. The shorter table decides the tier count.
- `WORKFLOWS_EMAIL_TIER_MIN_DAYS_AT_TIER`: per-tier dwell before promotion, comma-separated, clamped to the last entry.
- Promotion and demotion knobs: `WORKFLOWS_EMAIL_TIER_RATE_WINDOW_DAYS` (promotion window), `WORKFLOWS_EMAIL_TIER_DEMOTION_WINDOW_DAYS`, `WORKFLOWS_EMAIL_TIER_DEMOTION_COOLDOWN_DAYS` (keep at least as long as the demotion window), `WORKFLOWS_EMAIL_TIER_INACTIVITY_DECAY_DAYS` (0 disables decay), `WORKFLOWS_EMAIL_TIER_MIN_ACTIVE_DAYS`, `WORKFLOWS_EMAIL_TIER_MIN_DAILY_USE_RATIO`, `WORKFLOWS_EMAIL_TIER_MAX_COMPLAINT_RATE`, `WORKFLOWS_EMAIL_TIER_MAX_BOUNCE_RATE`, `WORKFLOWS_EMAIL_TIER_COMPLAINT_RATE_MIN_SENDS`, `WORKFLOWS_EMAIL_TIER_COMPLAINT_COUNT_BACKSTOP`, `WORKFLOWS_EMAIL_TIER_BOUNCE_RATE_MIN_SENDS`.
- `HOGFLOW_BATCH_TRIGGER_ELEVATED_TEAM_IDS`: the pre-tier allowlist. It overrides the tier entirely, so a saved tier does nothing for a listed team.
@@ -39,10 +39,10 @@ Django (`posthog/settings/web.py`):
Worker (`nodejs/src/cdp/config.ts`):
- `EMAIL_TEAM_SENDING_CAP_MODE`: `off` (default), `shadow`, or `enforce`.
-- `EMAIL_TEAM_SENDING_CAP_HOURLY_BY_TIER`, `EMAIL_TEAM_SENDING_CAP_DAILY_BY_TIER`: must mirror the Django tables. An unusable table turns the cap off rather than applying a wrong number.
+- `EMAIL_TEAM_SENDING_CAP_DAILY_BY_TIER`: must mirror the Django table. An unusable table, such as one with a non-integer entry, falls back to the worker's built-in default table.
All of these reach production as environment variables through `posthog/charts` (with any secret values via `posthog/secrets`).
-None of them are wired there yet; the charts change is part of turning the rollout mode on, not part of merging the code.
+Charts sets both modes to `enforce` in every environment, so the rollout order below is complete there. The cap tables are not set there, so each side runs on its code defaults, and a change to a default table takes effect on deploy.
## Decision rules the sweep applies
@@ -55,15 +55,15 @@ Decay, suspension drops, admin recomputes, and the backfill stay silent.
## Transactional email
-An email step categorized as transactional is never delayed by the send-time buckets, in any mode.
+An email step categorized as transactional is never delayed by the send-time bucket, in any mode.
A password reset or a receipt that arrives two hours late has already failed the person waiting for it, so pacing it achieves nothing that dropping it would not.
This matches the billing quota, which transactional email already bypasses.
-The send still drains both buckets by what it costs, so transactional volume displaces the project's marketing while tokens remain.
+The send still drains the bucket by what it costs, so transactional volume displaces the project's marketing while tokens remain.
A project that spends its whole allowance on transactional email has nothing left for marketing, which is the intended trade.
The charge does not bound the exemption.
-The buckets record no debt, so once a project empties them its further transactional sends cost nothing and this cap stops pacing it.
+The bucket records no debt, so once a project empties it further transactional sends cost nothing and this cap stops pacing it.
A project that labels all of its email transactional is therefore not paced per team at all.
No other control bounds that volume per project either.
The SES account rate limiter, which every send still passes, paces the whole account rather than one project.
@@ -83,21 +83,21 @@ A project appearing there often is spending more on transactional than its tier
2. Run `python manage.py backfill_workflows_email_sending_tiers` per region, read the printed distribution, then re-run with `--apply`. This lands established senders on their earned tier in one step.
3. Set both modes to `shadow` via charts. Nothing is delayed; would-be delays log and count in `cdp_team_email_cap_delayed_total{mode="shadow"}`. Watch that against real traffic.
4. Set both modes to `enforce`. Enforcement applies to every team at once; the Reputation tab's allowance card appears at this point.
- Never set the Django mode to `enforce` on a deployment whose email worker does not carry the send-time caps: the batch audience cap alone can be sidestepped by editing a workflow while a batch is queued, and the send-time buckets are what bound that.
+ Never set the Django mode to `enforce` on a deployment whose email worker does not carry the send-time caps: the batch audience cap alone can be sidestepped by editing a workflow while a batch is queued, and the send-time bucket is what bounds that.
5. To back out, set the modes back to `off`; the tiers keep computing and nothing else changes.
## Known limits
-- The batch audience cap is decided when the batch is dispatched. Adding an email step to the workflow while a batch is queued does not re-cap it; the send-time buckets still cap every email at execution. This is why enforcement requires the worker caps to be deployed (see the rollout order).
-- Test-panel sends bypass the team buckets on purpose, matching the per-workflow rate limit.
+- The batch audience cap is decided when the batch is dispatched. Adding an email step to the workflow while a batch is queued does not re-cap it; the send-time bucket still caps every email at execution. This is why enforcement requires the worker caps to be deployed (see the rollout order).
+- Test-panel sends bypass the team bucket on purpose, matching the per-workflow rate limit.
- Rescheduled emails keep their email queue priority while waiting. After a team-cap, workflow-pacing, or SES-throttle retry, the workflow restores its origin queue and priority when it next leaves the email queue. A push notification retried while the workflow is on the email queue behaves the same way and waits at the priority of its own message category.
- Transactional sends are charged but never delayed, so a team whose transactional volume alone exceeds its tier can hold its own marketing at zero (see Transactional email below).
-- The buckets are token buckets: a full idle bucket plus refill allows up to roughly twice the stated cap in the very first period. The bucket TTLs exceed the refill periods so this does not recur from idling.
-- A denied send parks until every short bucket has refilled enough to cover it, instead of retrying on a fixed few-minute cadence.
+- The bucket is a token bucket: a full idle bucket plus refill allows up to roughly twice the stated cap in the very first period. The bucket TTL exceeds the refill period so this does not recur from idling.
+- A denied send parks until the bucket has refilled enough to cover it, instead of retrying on a fixed few-minute cadence.
The computed wait is capped at one hour and then jittered 1x to 2x, so a parked send can wait just under two hours between attempts.
The wait reserves nothing: a competing send can take the tokens first, and the send parks again.
Capacity that arrives early is only noticed when the send wakes.
After a manual tier raise, a capped team's backlog can sit still for up to two hours.
- A send denied because the limiter itself failed keeps the shorter token bucket cadence, at most 5 to 10 minutes.
+ A send denied because the limiter itself failed keeps the token bucket cadence, at most 5 to 10 minutes.
- Gmail provides no per-message feedback loop, so complaint rates (ours and AWS's) cannot see Gmail complaints at all.
-- The `HOGFLOW_BATCH_TRIGGER_ELEVATED_TEAM_IDS` allowlist elevates a team to the top tier in Django only: the UI, the admin, and the batch audience cap show top-tier numbers, but the worker's send-time buckets read the stored tier. An allowlisted team below the top tier is therefore throttled at its stored tier while being told otherwise, and its shadow-mode delay counts overstate real impact. Before enforcing, pin each allowlisted team at the top tier from the Django admin and empty the allowlist, rather than plumbing the list into the worker.
+- The `HOGFLOW_BATCH_TRIGGER_ELEVATED_TEAM_IDS` allowlist elevates a team to the top tier in Django only: the UI, the admin, and the batch audience cap show top-tier numbers, but the worker's send-time bucket reads the stored tier. An allowlisted team below the top tier is therefore throttled at its stored tier while being told otherwise, and its shadow-mode delay counts overstate real impact. Before enforcing, pin each allowlisted team at the top tier from the Django admin and empty the allowlist, rather than plumbing the list into the worker.
diff --git a/frontend/snapshots.yml b/frontend/snapshots.yml
index e4d5265c7db0..f9b0ce2b7fb8 100644
--- a/frontend/snapshots.yml
+++ b/frontend/snapshots.yml
@@ -8615,25 +8615,25 @@ snapshots:
products-workflows-editor-tile-canvas--with-step-counts--light:
hash: v1.k794b7964.50beae04f0b949a710da41fdca70c671369ae0ac0499d284b69e1c57e931f1bc.o27SKj0cbEgIAZ6OSgXLX9_lFEaYUAWLmXef1W0TB3w
products-workflows-reputation--domain-withheld-from-caller--dark:
- hash: v1.k794b7964.4c8ae4bd60867d552c0b0499308c93dbb6a9e6da74929a97ddbedd39f992599b.bwSgpaQEan0zikdVKGPrgdoZQY5PMjSXnsfOVCyrrVc
+ hash: v1.k794b7964.d53a085a1aa52aa8a6f9b11139a9137e519f62777e40416911312dcf0f5e8c59.br5ro0a-wGiss4yFsj7ufw9hpky2h61ILHW6lPgs9-Q
products-workflows-reputation--domain-withheld-from-caller--light:
- hash: v1.k794b7964.147be54ef11f884bd92df02007bd66822377032ba8071d828df3f94cf7a99f84.k0-DsLWiwxjImrUNIp6nmGzckC9i8zgG5syjjW6BmUg
+ hash: v1.k794b7964.e4138f29c6fff6c368519b043d012a89f7747a6465e16566834cdf07cc12a03a.stFzc8LAwBI3OXbdWu_shXLaQDi4vauzKfqq8bY2HTw
products-workflows-reputation--no-provider-data--dark:
- hash: v1.k794b7964.5b437cfe30305fcb667b209851f1356a4cc10702438516128c4884809094a31c.SlR1rH9HLvxf1-vLydVP3VX55FWrTQaTsOERMs6J6Ac
+ hash: v1.k794b7964.1bcb2e6ef83b119dba06d4802b925640fbb595dbf8140dcb358dbb8871dd09f4.hDt0DCLyLnmJ82WFN-BIVGytHIFtv6UNpUe3zDtvl1I
products-workflows-reputation--no-provider-data--light:
- hash: v1.k794b7964.1d1e5429cc3922b93b9452c8d0204fd2f4f8b776f806a0f4b7f1cd40baf73ae7.sbnZcNLID6RiaQvAvEgFsse3O7oDWAD785JScfbnZBI
+ hash: v1.k794b7964.a3d1800c6b887408a219b73d0832c2735c092b4a5f7e9c090067ac31c4e63114.rLx8LU8E5ix6a1r-f0I-5YSHu4q_vAesNIG23WPG2hk
products-workflows-reputation--one-provider-filtering--dark:
- hash: v1.k794b7964.c903e5bcfbad8781cc5dd80b7818e413ed9b11e69d8186502221199d1a1dfae0.LYWxf9d9Xjg5HZlNKrdOrt1sXMwtbecPpVzNhJOuWiE
+ hash: v1.k794b7964.efcfd2b700a73cf93c9e2621f987432ea15d65ec3407427c81d2f59b9f7a3d75.Bns_6SK_6iWrgfLLraC6qSUFI6RrxECYwpK_1hPqX3U
products-workflows-reputation--one-provider-filtering--light:
- hash: v1.k794b7964.f5d9f9e0c0117059d3362bfc84a42e10076f27585acf75aeeafc2d000e62e028.V2RMl0YHbLFf654ctsE8yLgeCoRMPOXM_pPlideqrio
+ hash: v1.k794b7964.3b2ff5c425aaa448dfaae2d25b021e878b8daf88abd9267cfca9c99fd3320712.rrJWu13vHAJFCRdLpkCPmpifm36D5_GO-e-rzOwJ7Bo
products-workflows-reputation--provider-data-without-workflow-rates--dark:
- hash: v1.k794b7964.9f3f4aa8a8dbc982d909a6570ed3247f7b9cf541dc7de06af7001bdb7d03d8bc.S9PFsharMlX3fTlNYtcVJXaH-_kuiPglS-CEcsJJDHY
+ hash: v1.k794b7964.a47f8fa08660ff440cc6372ac11cf3e501987b909b87cd69fb0548b3913ea82c.VkUZDslZPWT472UtLCevbZ0qIIbafYD2LB7TZzU6xXU
products-workflows-reputation--provider-data-without-workflow-rates--light:
- hash: v1.k794b7964.b93a6572a6999592d2daef92c38b576457067ac50f9a5419b3bc080e676668fa.3dfOSKmnjzpqrCoPFuFEh_6bXkrktysPL7_cnF7gKvs
+ hash: v1.k794b7964.79be1d4125e9a508c3c1343cdf0df9c2b3e4479a35e5959bd2729371a5ebdbd8.glDPB4iFYAMcZ5s2G5Qydhbw4-e1cZEVWYnWmbvgGh0
products-workflows-reputation--shared-sending-domain--dark:
- hash: v1.k794b7964.cdce03b8be8c4ffeef15eb0a6bcab206c7eb5b1cd8b8852b1aca0de497732226.6biyQXJiwnyQcZZtOgCOVH3hpDAfJp6K_L06WtP_aW8
+ hash: v1.k794b7964.0b29efa4fa64a34330301e2edad47b510e18c404d52e94944ceffb116b0a7f87.mj6mh_2Ih-cuMXn0DNe2q0Ca-ZYrl_ppsKkPnwOav0w
products-workflows-reputation--shared-sending-domain--light:
- hash: v1.k794b7964.e029f36f5a4cf022e888be7cfa04b7ef2741414b6205173b0d879b037b3663df.FJeja9fI99Dhe5aX-g4hQp6P3oGBNjviDjw14YhV0cY
+ hash: v1.k794b7964.14c3a0bdee027f6b6e0f6ae8cfcf7cfe9f9b921f2f23fdec40b1bbe31da65181.CVIMhkIu0ZZyuE8e58rpxkZMTFw3auhqL3A0C3vNcxQ
products-workflows-send-calendar--busy-week--dark:
hash: v1.k794b7964.1edf0999ab5e390b86d0a8d48ab5821c5cb291b35eba58eb4000587652ba79af.4plcEAYl06VvPXCtAKWYvMcbQLWV-U1_khdj3SHu5Ho
products-workflows-send-calendar--busy-week--light:
diff --git a/posthog/admin/admins/team_admin.py b/posthog/admin/admins/team_admin.py
index a158873ec895..d531e23627b6 100644
--- a/posthog/admin/admins/team_admin.py
+++ b/posthog/admin/admins/team_admin.py
@@ -968,11 +968,10 @@ class TeamAdmin(admin.ModelAdmin):
"team is removed from it."
)
return format_html(
- "<strong>Tier {}</strong> of {} — {} emails/hour, {} emails/day, "
+ "<strong>Tier {}</strong> of {} — {} emails/day, "
"{} max batch audience<br>Set at: {}<br>Pinned: {}<br>Rollout mode: <code>{}</code>{}",
tier,
max_email_sending_tier(),
- f"{limits.per_hour:,}",
f"{limits.per_day:,}",
f"{limits.max_batch_audience:,}",
updated_at.isoformat() if updated_at else "never (team has not been evaluated yet)",
@@ -989,7 +988,6 @@ class TeamAdmin(admin.ModelAdmin):
tiers = [
{
"tier": tier,
- "per_hour": f"{get_email_sending_tier_limits(tier).per_hour:,}",
"per_day": f"{get_email_sending_tier_limits(tier).per_day:,}",
"selected": tier == (state.tier if state else 0),
}
diff --git a/posthog/settings/web.py b/posthog/settings/web.py
index 165c2567b749..64e4a9f26e1a 100644
--- a/posthog/settings/web.py
+++ b/posthog/settings/web.py
@@ -1169,20 +1169,14 @@ HOGFLOW_BATCH_TRIGGER_ELEVATED_TEAM_IDS: set[int] = {
# at tier 0 and earns the next tier by sending cleanly over time, which bounds how much damage an
# unproven team can do and keeps its early volume small enough that complaint feedback (which lags
# by hours) arrives while total volume is still low.
-# The three lists are indexed by tier and must all be the same length. The top tier matches
+# Both lists are indexed by tier and must be the same length. The top tier matches
# HOGFLOW_BATCH_TRIGGER_LIMIT_ELEVATED so a fully graduated team is no more limited than it was
# before tiers existed. Adjacent tiers stay roughly 3x apart: published warmup ramps (SendGrid,
# Mailgun, Oracle) grow 25-50% per step and warn against jumps above 2x, and a promotion is an
# overnight allowance jump, so a 3x step with the utilization bar below approximates that ramp
-# while keeping the tier count small enough to reason about. Two deliberate exceptions at the
-# bottom: tier 0 is a 100/day probation tier for completely unproven domains (SendGrid trials
-# start at 100/day, Customer.io at 200), and its hourly cap is half the daily cap rather than the
-# usual fifth so a first real send does not crawl at 20 an hour. The 10x step off tier 0 is fine
-# at that absolute volume.
-WORKFLOWS_EMAIL_TIER_HOURLY_CAPS: list[int] = [
- int(cap)
- for cap in get_list(get_from_env("WORKFLOWS_EMAIL_TIER_HOURLY_CAPS", "50,200,600,2000,6000,20000,60000,200000"))
-]
+# while keeping the tier count small enough to reason about. Tier 0 is a 100/day probation tier
+# for completely unproven domains (SendGrid trials start at 100/day, Customer.io at 200), so the
+# 10x step off it is fine at that absolute volume.
WORKFLOWS_EMAIL_TIER_DAILY_CAPS: list[int] = [
int(cap)
for cap in get_list(
diff --git a/posthog/tasks/email.py b/posthog/tasks/email.py
index 75a0148c63f4..32cc7e503649 100644
--- a/posthog/tasks/email.py
+++ b/posthog/tasks/email.py
@@ -1095,11 +1095,13 @@ def send_email_sending_unsuspended(team_id: int, unsuspended_at: str) -> None:
@shared_task(**EMAIL_TASK_KWARGS)
@with_team_scope()
-def send_email_sending_tier_demoted(team_id: int, per_day: int, per_hour: int, demoted_at: str) -> None:
+def send_email_sending_tier_demoted(team_id: int, per_day: int, demoted_at: str, per_hour: int = 0) -> None:
"""
Tell a project's admins that its workflow email sending limit was lowered for deliverability
problems. Admin+ recipients and no notification-setting gate, matching the suspension emails:
the limit stays down until someone acts on the list quality.
+
+ `per_hour` is accepted and ignored so a task queued by an older release still deserializes.
"""
if not is_email_available(with_absolute_urls=True):
return
@@ -1114,7 +1116,6 @@ def send_email_sending_tier_demoted(team_id: int, per_day: int, per_hour: int, d
template_context={
"team": team,
"per_day": f"{per_day:,}",
- "per_hour": f"{per_hour:,}",
"reputation_path": f"/project/{team.id}/workflows/reputation",
},
)
diff --git a/posthog/tasks/test/test_email.py b/posthog/tasks/test/test_email.py
index b782b4775735..a1a526a3bbcb 100644
--- a/posthog/tasks/test/test_email.py
+++ b/posthog/tasks/test/test_email.py
@@ -35,6 +35,7 @@ from posthog.tasks.email import (
send_discussions_mentioned,
send_email_change_emails,
send_email_sending_reputation_finding,
+ send_email_sending_tier_demoted,
send_email_verification_code,
send_external_data_failure_digest,
send_fatal_plugin_error,
@@ -251,6 +252,27 @@ class TestEmail(APIBaseTest, ClickhouseTestMixin):
assert len(mocked_email_messages) == 2
assert (mocked_email_messages[0].campaign_key == mocked_email_messages[1].campaign_key) is deduped
+ @parameterized.expand(
+ [
+ ("current_release_kwargs", {}),
+ ("older_release_kwargs_with_per_hour", {"per_hour": 200}),
+ ]
+ )
+ def test_send_email_sending_tier_demoted_names_only_the_daily_limit(
+ self, MockEmailMessage: MagicMock, _name: str, extra_kwargs: dict[str, int]
+ ) -> None:
+ mocked_email_messages = mock_email_messages(MockEmailMessage)
+ self.organization_membership.level = OrganizationMembership.Level.ADMIN
+ self.organization_membership.save()
+
+ send_email_sending_tier_demoted(
+ team_id=self.team.id, per_day=1000, demoted_at="2026-01-05T07:15:00+00:00", **extra_kwargs
+ )
+
+ assert len(mocked_email_messages) == 1
+ assert "1,000 emails per day" in mocked_email_messages[0].html_body
+ assert "per hour" not in mocked_email_messages[0].html_body
+
def test_send_delegation_invite_falls_back_when_organization_name_is_a_url(
self, MockEmailMessage: MagicMock
) -> None:
diff --git a/posthog/templates/admin/posthog/team/email_sending_tier_actions.html b/posthog/templates/admin/posthog/team/email_sending_tier_actions.html
index a288ee6df96e..f3c247516684 100644
--- a/posthog/templates/admin/posthog/team/email_sending_tier_actions.html
+++ b/posthog/templates/admin/posthog/team/email_sending_tier_actions.html
@@ -11,7 +11,7 @@ outer form (no <form> of their own, which the browser would drop) and submit thr
<select id="email_sending_tier" name="tier">
{% for option in tiers %}
<option value="{{ option.tier }}" {% if option.selected %}selected{% endif %}>
- {{ option.tier }} — {{ option.per_hour }}/hour, {{ option.per_day }}/day
+ {{ option.tier }} — {{ option.per_day }}/day
</option>
{% endfor %}
</select>
diff --git a/posthog/templates/email/email_sending_tier_demoted.html b/posthog/templates/email/email_sending_tier_demoted.html
index 3fe2a7c3a0dd..51807164d8b8 100644
--- a/posthog/templates/email/email_sending_tier_demoted.html
+++ b/posthog/templates/email/email_sending_tier_demoted.html
@@ -3,7 +3,7 @@
{% block section %}
<!-- prettier-ignore -->
<p>
- Recent workflow emails from project <b>{{ team }}</b> caused deliverability problems, such as spam complaints or bounced addresses. To protect your sending reputation, we lowered the project's sending limit to <b>{{ per_day }} emails per day</b> ({{ per_hour }} per hour).
+ Recent workflow emails from project <b>{{ team }}</b> caused deliverability problems, such as spam complaints or bounced addresses. To protect your sending reputation, we lowered the project's sending limit to <b>{{ per_day }} emails per day</b>.
</p>
<p>Your workflows keep running. Emails over the limit are delayed and sent when capacity frees up, not dropped.</p>
<p><b>How to get the limit back up</b></p>
diff --git a/products/workflows/backend/facade/contracts.py b/products/workflows/backend/facade/contracts.py
index a3b781cb9256..bfc7d1bf7b44 100644
--- a/products/workflows/backend/facade/contracts.py
+++ b/products/workflows/backend/facade/contracts.py
@@ -289,10 +289,9 @@ class PeopleImportSummary:
@frozen
class EmailSendingTierLimits:
- """What a trust tier allows: two send-rate caps and a maximum batch audience."""
+ """What a trust tier allows: a daily send cap and a maximum batch audience."""
tier: int
- per_hour: int
per_day: int
max_batch_audience: int
@@ -338,10 +337,8 @@ class EmailSendingAllowance:
tier: int
max_tier: int
- emails_per_hour: int
emails_per_day: int
max_batch_audience: int
- emails_sent_last_hour: int
emails_sent_last_day: int
enforced: bool
diff --git a/products/workflows/backend/management/commands/backfill_workflows_email_sending_tiers.py b/products/workflows/backend/management/commands/backfill_workflows_email_sending_tiers.py
index 64f6518c0c88..f4cc7e846ab4 100644
--- a/products/workflows/backend/management/commands/backfill_workflows_email_sending_tiers.py
+++ b/products/workflows/backend/management/commands/backfill_workflows_email_sending_tiers.py
@@ -217,7 +217,7 @@ class Command(BaseCommand):
share = (count / sending_teams * 100) if sending_teams else 0.0
self.stdout.write(
f" tier {tier}: {count:>6} teams ({share:5.1f}%) "
- f"{limits.per_hour:>9,}/hour {limits.per_day:>10,}/day {limits.max_batch_audience:>10,} batch"
+ f"{limits.per_day:>10,}/day {limits.max_batch_audience:>10,} batch"
)
self.stdout.write("")
diff --git a/products/workflows/backend/models/team_workflows_config.py b/products/workflows/backend/models/team_workflows_config.py
index 8ecf23d8b21d..7f7f2b2163e1 100644
--- a/products/workflows/backend/models/team_workflows_config.py
+++ b/products/workflows/backend/models/team_workflows_config.py
@@ -35,8 +35,8 @@ class TeamWorkflowsConfig(models.Model):
ses_tenant_reputation_impact = models.CharField(max_length=32, blank=True, default="", db_default="")
ses_tenant_state_synced_at = models.DateTimeField(null=True, blank=True)
- # Trust tier for workflow email. The tier picks the team's hourly cap, daily cap and maximum
- # batch audience from the tables in settings, so an unproven team cannot send fast enough to
+ # Trust tier for workflow email. The tier picks the team's daily cap and maximum batch
+ # audience from the tables in settings, so an unproven team cannot send fast enough to
# damage the shared SES account's reputation. Every team starts at 0 and a periodic task moves
# it one step at a time based on how much it sent and how clean the sending was.
# db_default so raw INSERTs from non-Django writers keep working.
diff --git a/products/workflows/backend/presentation/views/hog_flow.py b/products/workflows/backend/presentation/views/hog_flow.py
index 243925de57c8..e5899d5659bc 100644
--- a/products/workflows/backend/presentation/views/hog_flow.py
+++ b/products/workflows/backend/presentation/views/hog_flow.py
@@ -3015,14 +3015,10 @@ class EmailSendingAllowanceSerializer(serializers.Serializer):
max_tier = serializers.IntegerField(
read_only=True, help_text="The highest tier there is, so the current tier can be shown as progress."
)
- emails_per_hour = serializers.IntegerField(read_only=True, help_text="How many emails this tier allows per hour.")
emails_per_day = serializers.IntegerField(read_only=True, help_text="How many emails this tier allows per day.")
max_batch_audience = serializers.IntegerField(
read_only=True, help_text="The largest audience this tier allows for a single batch send."
)
- emails_sent_last_hour = serializers.IntegerField(
- read_only=True, help_text="Emails sent by this project's workflows in the last hour."
- )
emails_sent_last_day = serializers.IntegerField(
read_only=True, help_text="Emails sent by this project's workflows in the last 24 hours."
)
diff --git a/products/workflows/backend/services/email_health.py b/products/workflows/backend/services/email_health.py
index 3b83c79e9875..cc91fbc1db0c 100644
--- a/products/workflows/backend/services/email_health.py
+++ b/products/workflows/backend/services/email_health.py
@@ -67,7 +67,7 @@ def team_email_sending_allowance(team_id: int) -> EmailSendingAllowance:
keystroke while these two aggregations do not depend on the search.
"""
# Entries are pickles: bump the version when EmailSendingAllowance changes module or shape.
- cache_key = f"workflows_email_sending_allowance_v2_{team_id}"
+ cache_key = f"workflows_email_sending_allowance_v3_{team_id}"
cached = cache.get(cache_key)
if cached is not None:
return cached
@@ -77,10 +77,8 @@ def team_email_sending_allowance(team_id: int) -> EmailSendingAllowance:
allowance = EmailSendingAllowance(
tier=resolved.tier,
max_tier=max_email_sending_tier(),
- emails_per_hour=resolved.limits.per_hour,
emails_per_day=resolved.limits.per_day,
max_batch_audience=resolved.limits.max_batch_audience,
- emails_sent_last_hour=_team_email_sends_since(team_id, now - timedelta(hours=1)),
emails_sent_last_day=_team_email_sends_since(team_id, now - timedelta(days=1)),
enforced=resolved.enforced,
)
diff --git a/products/workflows/backend/services/email_sending_tier_notifications.py b/products/workflows/backend/services/email_sending_tier_notifications.py
index 388a0a58414a..8867cc2c7aea 100644
--- a/products/workflows/backend/services/email_sending_tier_notifications.py
+++ b/products/workflows/backend/services/email_sending_tier_notifications.py
@@ -52,7 +52,6 @@ def _notify_demotion(decision: TierDecision) -> None:
send_email_sending_tier_demoted.delay(
team_id=decision.team_id,
per_day=limits.per_day,
- per_hour=limits.per_hour,
demoted_at=timezone.now().isoformat(),
)
except Exception:
@@ -83,10 +82,7 @@ def _notify_promotion(decision: TierDecision) -> None:
notification_type=NotificationType.EMAIL_REPUTATION,
priority=Priority.NORMAL,
title="Workflow email sending limit raised",
- body=(
- f"This project earned a higher sending limit: "
- f"up to {limits.per_day:,} emails per day and {limits.per_hour:,} per hour."
- ),
+ body=f"This project earned a higher sending limit: up to {limits.per_day:,} emails per day.",
target_type=TargetType.TEAM,
target_id=str(decision.team_id),
source_url="/workflows/reputation",
diff --git a/products/workflows/backend/test/test_email_sending_tier.py b/products/workflows/backend/test/test_email_sending_tier.py
index 21a1d1490b02..bda1b86136d6 100644
--- a/products/workflows/backend/test/test_email_sending_tier.py
+++ b/products/workflows/backend/test/test_email_sending_tier.py
@@ -28,12 +28,10 @@ from products.workflows.backend.services.email_sending_tier import (
from products.workflows.backend.tasks.email_sending_tiers import recompute_workflows_email_sending_tiers
from products.workflows.backend.utils.email_sending_tiers import get_email_sending_tier_limits
-TIER_HOURLY_CAPS = [200, 600, 2000, 6000, 20000, 60000, 200000]
TIER_DAILY_CAPS = [1000, 3000, 10000, 30000, 100000, 300000, 1000000]
TIER_BATCH_CAPS = [1000, 3000, 10000, 30000, 100000, 300000, 1000000]
TIER_SETTINGS = {
- "WORKFLOWS_EMAIL_TIER_HOURLY_CAPS": TIER_HOURLY_CAPS,
"WORKFLOWS_EMAIL_TIER_DAILY_CAPS": TIER_DAILY_CAPS,
"WORKFLOWS_EMAIL_TIER_BATCH_AUDIENCE_CAPS": TIER_BATCH_CAPS,
"WORKFLOWS_EMAIL_TIER_MIN_DAYS_AT_TIER": [3],
@@ -79,10 +77,10 @@ def clean_days(count: int, sent_per_day: int, *, days_ago: int = 0) -> dict[str,
@override_settings(**TIER_SETTINGS)
class TestEmailSendingTierDecision(SimpleTestCase):
- @parameterized.expand([(tier, caps) for tier, caps in enumerate(zip(TIER_HOURLY_CAPS, TIER_DAILY_CAPS))])
- def test_tier_maps_to_its_caps(self, tier: int, caps: tuple[int, int]) -> None:
+ @parameterized.expand([(tier, cap) for tier, cap in enumerate(TIER_DAILY_CAPS)])
+ def test_tier_maps_to_its_caps(self, tier: int, cap: int) -> None:
limits = get_email_sending_tier_limits(tier)
- assert (limits.per_hour, limits.per_day) == caps
+ assert limits.per_day == cap
@parameterized.expand([(tier,) for tier in range(len(TIER_DAILY_CAPS) - 1)])
def test_promotes_one_tier_when_every_criterion_is_met(self, tier: int) -> None:
diff --git a/products/workflows/backend/tests/api/test_email_reputation.py b/products/workflows/backend/tests/api/test_email_reputation.py
index 63822cdbb738..17c9ef068f37 100644
--- a/products/workflows/backend/tests/api/test_email_reputation.py
+++ b/products/workflows/backend/tests/api/test_email_reputation.py
@@ -72,7 +72,6 @@ class TestEmailReputationAPI(APIBaseTest):
allowance = data.pop("sending_allowance")
assert allowance["tier"] == 0
assert allowance["enforced"] is False
- assert allowance["emails_sent_last_hour"] == 0
assert allowance["emails_sent_last_day"] == 0
assert data == {
"aws": None,
diff --git a/products/workflows/backend/utils/email_sending_tiers.py b/products/workflows/backend/utils/email_sending_tiers.py
index 1131ca9b3376..a7cb6858d2e7 100644
--- a/products/workflows/backend/utils/email_sending_tiers.py
+++ b/products/workflows/backend/utils/email_sending_tiers.py
@@ -49,9 +49,8 @@ def min_days_at_tier(tier: int) -> int:
def _tier_count() -> int:
- # The shortest list wins so a partial env override cannot index past the end of another table.
+ # The shorter list wins so a partial env override cannot index past the end of the other table.
return min(
- len(settings.WORKFLOWS_EMAIL_TIER_HOURLY_CAPS),
len(settings.WORKFLOWS_EMAIL_TIER_DAILY_CAPS),
len(settings.WORKFLOWS_EMAIL_TIER_BATCH_AUDIENCE_CAPS),
)
@@ -70,7 +69,6 @@ def get_email_sending_tier_limits(tier: int) -> EmailSendingTierLimits:
elevated = settings.HOGFLOW_BATCH_TRIGGER_LIMIT_ELEVATED
return EmailSendingTierLimits(
tier=tier,
- per_hour=elevated,
per_day=elevated,
max_batch_audience=elevated,
)
@@ -78,7 +76,6 @@ def get_email_sending_tier_limits(tier: int) -> EmailSendingTierLimits:
clamped = min(max(tier, MIN_EMAIL_SENDING_TIER), count - 1)
return EmailSendingTierLimits(
tier=clamped,
- per_hour=settings.WORKFLOWS_EMAIL_TIER_HOURLY_CAPS[clamped],
per_day=settings.WORKFLOWS_EMAIL_TIER_DAILY_CAPS[clamped],
max_batch_audience=settings.WORKFLOWS_EMAIL_TIER_BATCH_AUDIENCE_CAPS[clamped],
)
diff --git a/products/workflows/frontend/Workflows/Reputation/WorkflowsReputation.stories.tsx b/products/workflows/frontend/Workflows/Reputation/WorkflowsReputation.stories.tsx
index 9f3014c39def..8603ec4c766e 100644
--- a/products/workflows/frontend/Workflows/Reputation/WorkflowsReputation.stories.tsx
+++ b/products/workflows/frontend/Workflows/Reputation/WorkflowsReputation.stories.tsx
@@ -96,10 +96,8 @@ const baseResponse: TeamEmailReputationResponseApi = {
sending_allowance: {
tier: 2,
max_tier: 4,
- emails_per_hour: 5000,
emails_per_day: 50000,
max_batch_audience: 25000,
- emails_sent_last_hour: 1200,
emails_sent_last_day: 18400,
enforced: true,
},
diff --git a/products/workflows/frontend/Workflows/Reputation/WorkflowsReputation.tsx b/products/workflows/frontend/Workflows/Reputation/WorkflowsReputation.tsx
index 2cece1b41e2a..b05bd41aa5ee 100644
--- a/products/workflows/frontend/Workflows/Reputation/WorkflowsReputation.tsx
+++ b/products/workflows/frontend/Workflows/Reputation/WorkflowsReputation.tsx
@@ -379,7 +379,6 @@ function TeamRatesCard({
function SendingAllowanceCard({ allowance }: { allowance: EmailSendingAllowanceApi }): JSX.Element {
const { canRequestSendingTierIncrease } = useValues(workflowsReputationLogic)
const { requestSendingTierIncrease } = useActions(workflowsReputationLogic)
- const hourlyPercent = Math.min(100, (allowance.emails_sent_last_hour / allowance.emails_per_hour) * 100)
const dailyPercent = Math.min(100, (allowance.emails_sent_last_day / allowance.emails_per_day) * 100)
return (
<div className="border rounded p-4 bg-surface-primary" data-attr="workflows-sending-allowance">
@@ -408,17 +407,6 @@ function SendingAllowanceCard({ allowance }: { allowance: EmailSendingAllowanceA
)}
</p>
<div className="flex flex-wrap gap-8 mt-3">
- <div className="min-w-48">
- <MetricLabel
- label="Emails this hour"
- tooltip="Emails your workflows sent in the last hour, against what this tier allows per hour."
- />
- <div className="text-lg font-semibold">
- {humanFriendlyNumber(allowance.emails_sent_last_hour)} of{' '}
- {humanFriendlyNumber(allowance.emails_per_hour)}
- </div>
- <LemonProgress percent={hourlyPercent} className="mt-1" />
- </div>
<div className="min-w-48">
<MetricLabel
label="Emails today"
diff --git a/products/workflows/frontend/Workflows/Reputation/workflowsReputationLogic.test.ts b/products/workflows/frontend/Workflows/Reputation/workflowsReputationLogic.test.ts
index ab2823cd479c..6eebf0372288 100644
--- a/products/workflows/frontend/Workflows/Reputation/workflowsReputationLogic.test.ts
+++ b/products/workflows/frontend/Workflows/Reputation/workflowsReputationLogic.test.ts
@@ -16,10 +16,8 @@ import { workflowsReputationLogic } from './workflowsReputationLogic'
const allowance: EmailSendingAllowanceApi = {
tier: 2,
max_tier: 4,
- emails_per_hour: 5000,
emails_per_day: 50000,
max_batch_audience: 25000,
- emails_sent_last_hour: 1200,
emails_sent_last_day: 18400,
enforced: true,
}
diff --git a/products/workflows/frontend/Workflows/Reputation/workflowsReputationLogic.ts b/products/workflows/frontend/Workflows/Reputation/workflowsReputationLogic.ts
index 6bd5ace070f0..04553ba3bf94 100644
--- a/products/workflows/frontend/Workflows/Reputation/workflowsReputationLogic.ts
+++ b/products/workflows/frontend/Workflows/Reputation/workflowsReputationLogic.ts
@@ -45,7 +45,6 @@ function sendingTierIncreaseContext(
`Project ID: ${projectId ?? 'unknown'}`,
`Current tier: ${allowance.tier} of ${allowance.max_tier}`,
`Emails today: ${humanFriendlyNumber(allowance.emails_sent_last_day)} of ${humanFriendlyNumber(allowance.emails_per_day)}`,
- `Emails this hour: ${humanFriendlyNumber(allowance.emails_sent_last_hour)} of ${humanFriendlyNumber(allowance.emails_per_hour)}`,
...(rates
? [
`Bounce rate (last 30 days): ${percentage(rates.bounce_rate, 2, true)}`,
diff --git a/products/workflows/frontend/generated/api.schemas.ts b/products/workflows/frontend/generated/api.schemas.ts
index da6ae712f135..33396ba50350 100644
--- a/products/workflows/frontend/generated/api.schemas.ts
+++ b/products/workflows/frontend/generated/api.schemas.ts
@@ -2267,14 +2267,10 @@ export interface EmailSendingAllowanceApi {
readonly tier: number
/** The highest tier there is, so the current tier can be shown as progress. */
readonly max_tier: number
- /** How many emails this tier allows per hour. */
- readonly emails_per_hour: number
/** How many emails this tier allows per day. */
readonly emails_per_day: number
/** The largest audience this tier allows for a single batch send. */
readonly max_batch_audience: number
- /** Emails sent by this project's workflows in the last hour. */
- readonly emails_sent_last_hour: number
/** Emails sent by this project's workflows in the last 24 hours. */
readonly emails_sent_last_day: number
/** True when these allowances are applied to sends. False while they are only being measured. */
diff --git a/products/workflows/mcp/tools.yaml b/products/workflows/mcp/tools.yaml
index 4901622bf48e..3365606d0476 100644
--- a/products/workflows/mcp/tools.yaml
+++ b/products/workflows/mcp/tools.yaml
@@ -565,16 +565,15 @@ tools:
enabled: true
title: Get email reputation and sending allowance
description: >
- The project's workflow email health over the last 30 days and its sending allowance: tier, hourly and daily
- email caps, largest batch audience, and usage. Call it before planning a batch send or broadcast, and tell
- the user when the audience or volume would go over a cap. The caps apply only while
- sending_allowance.enforced is true; while it is false they are measured but not applied. Pass
- fields=['sending_allowance'] when that is all you need. Tiers rise on their own with a clean sending record.
- To get more sooner, the user can request a higher allowance in Workflows > Messaging > Reputation; the link
- shows while the caps are enforced, to accounts that can open a support ticket. Also returns bounce and
- complaint rates (project-wide and per workflow, worst first), the AWS SES verdict, per-mailbox-provider
- health, and any suspension. sending_allowance, aws and reputation are null for a user without project-wide
- workflow access.
+ The project's workflow email health over the last 30 days and its sending allowance: tier, daily email cap,
+ largest batch audience, and usage. Call it before planning a batch send or broadcast, and tell the user when
+ the audience or volume would go over a cap. The caps apply only while sending_allowance.enforced is true;
+ while it is false they are measured but not applied. Pass fields=['sending_allowance'] when that is all you
+ need. Tiers rise on their own with a clean sending record. To get more sooner, the user can request a higher
+ allowance in Workflows > Messaging > Reputation; the link shows while the caps are enforced, to accounts
+ that can open a support ticket. Also returns bounce and complaint rates (project-wide and per workflow,
+ worst first), the AWS SES verdict, per-mailbox-provider health, and any suspension. sending_allowance, aws
+ and reputation are null for a user without project-wide workflow access.
feature_flag: workflows-sending-tier-requests
response:
include:
diff --git a/services/mcp/schema/generated-tool-definitions.json b/services/mcp/schema/generated-tool-definitions.json
index a97b8b77cca3..1cdca784086b 100644
--- a/services/mcp/schema/generated-tool-definitions.json
+++ b/services/mcp/schema/generated-tool-definitions.json
@@ -17359,7 +17359,7 @@
}
},
"workflows-reputation-get": {
- "description": "The project's workflow email health over the last 30 days and its sending allowance: tier, hourly and daily email caps, largest batch audience, and usage. Call it before planning a batch send or broadcast, and tell the user when the audience or volume would go over a cap. The caps apply only while sending_allowance.enforced is true; while it is false they are measured but not applied. Pass fields=['sending_allowance'] when that is all you need. Tiers rise on their own with a clean sending record. To get more sooner, the user can request a higher allowance in Workflows > Messaging > Reputation; the link shows while the caps are enforced, to accounts that can open a support ticket. Also returns bounce and complaint rates (project-wide and per workflow, worst first), the AWS SES verdict, per-mailbox-provider health, and any suspension. sending_allowance, aws and reputation are null for a user without project-wide workflow access.",
+ "description": "The project's workflow email health over the last 30 days and its sending allowance: tier, daily email cap, largest batch audience, and usage. Call it before planning a batch send or broadcast, and tell the user when the audience or volume would go over a cap. The caps apply only while sending_allowance.enforced is true; while it is false they are measured but not applied. Pass fields=['sending_allowance'] when that is all you need. Tiers rise on their own with a clean sending record. To get more sooner, the user can request a higher allowance in Workflows > Messaging > Reputation; the link shows while the caps are enforced, to accounts that can open a support ticket. Also returns bounce and complaint rates (project-wide and per workflow, worst first), the AWS SES verdict, per-mailbox-provider health, and any suspension. sending_allowance, aws and reputation are null for a user without project-wide workflow access.",
"category": "Workflows",
"feature": "workflows",
"summary": "Get email reputation and sending allowance",
diff --git a/services/mcp/schema/tool-definitions-all.json b/services/mcp/schema/tool-definitions-all.json
index c135c816ea0b..1553590ff61b 100644
--- a/services/mcp/schema/tool-definitions-all.json
+++ b/services/mcp/schema/tool-definitions-all.json
@@ -18176,7 +18176,7 @@
}
},
"workflows-reputation-get": {
- "description": "The project's workflow email health over the last 30 days and its sending allowance: tier, hourly and daily email caps, largest batch audience, and usage. Call it before planning a batch send or broadcast, and tell the user when the audience or volume would go over a cap. The caps apply only while sending_allowance.enforced is true; while it is false they are measured but not applied. Pass fields=['sending_allowance'] when that is all you need. Tiers rise on their own with a clean sending record. To get more sooner, the user can request a higher allowance in Workflows > Messaging > Reputation; the link shows while the caps are enforced, to accounts that can open a support ticket. Also returns bounce and complaint rates (project-wide and per workflow, worst first), the AWS SES verdict, per-mailbox-provider health, and any suspension. sending_allowance, aws and reputation are null for a user without project-wide workflow access.",
+ "description": "The project's workflow email health over the last 30 days and its sending allowance: tier, daily email cap, largest batch audience, and usage. Call it before planning a batch send or broadcast, and tell the user when the audience or volume would go over a cap. The caps apply only while sending_allowance.enforced is true; while it is false they are measured but not applied. Pass fields=['sending_allowance'] when that is all you need. Tiers rise on their own with a clean sending record. To get more sooner, the user can request a higher allowance in Workflows > Messaging > Reputation; the link shows while the caps are enforced, to accounts that can open a support ticket. Also returns bounce and complaint rates (project-wide and per workflow, worst first), the AWS SES verdict, per-mailbox-provider health, and any suspension. sending_allowance, aws and reputation are null for a user without project-wide workflow access.",
"category": "Workflows",
"feature": "workflows",
"summary": "Get email reputation and sending allowance",
diff --git a/services/mcp/src/api/generated.ts b/services/mcp/src/api/generated.ts
index b54e9701fb1f..696f23d2be2f 100644
--- a/services/mcp/src/api/generated.ts
+++ b/services/mcp/src/api/generated.ts
@@ -37215,14 +37215,10 @@ export namespace Schemas {
readonly tier: number;
/** The highest tier there is, so the current tier can be shown as progress. */
readonly max_tier: number;
- /** How many emails this tier allows per hour. */
- readonly emails_per_hour: number;
/** How many emails this tier allows per day. */
readonly emails_per_day: number;
/** The largest audience this tier allows for a single batch send. */
readonly max_batch_audience: number;
- /** Emails sent by this project's workflows in the last hour. */
- readonly emails_sent_last_hour: number;
/** Emails sent by this project's workflows in the last 24 hours. */
readonly emails_sent_last_day: number;
/** True when these allowances are applied to sends. False while they are only being measured. */