improvement(billing): share the enterprise reporting usage read across processes

[waleedlatif1]

Summary

• Enterprise reporting-window usage sums (a year-long ledger scan) are now shared across processes through Redis with a 30s TTL. Trigger.dev runs every task in a fresh process, so the existing in-process LRU was always cold there, and the scan ran on nearly every document-processing and execution admission check
• The in-process LRU stays in front and still coalesces concurrent misses. The Redis GET has a 250ms deadline, and any Redis error, timeout, or unreadable value falls through to the exact sum. The write is a fire-and-forget SET … NX with a jittered TTL, so a slower, older sum never overwrites a fresher one or extends its life. There is no lock or lease
• The usage threshold email is now level-triggered, instead of being edge-triggered off an exact before/after org sum on every workflow completion. A claim keyed on (billing period, limit) (claimCreditsThreshold) sends each threshold at most once. A new period or a changed limit re-arms it with no reset write, and concurrent completions can't both send
• Recipients are resolved before claiming, so a period's email isn't used up when nobody can receive it. Zero-cost completions don't claim. The personal usage baseline and the claimed period come from the same billing context
• Invoicing, cycle close, overage, and threshold billing still read the ledger exactly
• Rollout note: accounts already at or above 80% this billing period get one threshold email after deploy; there is no backfill

Type of Change

• Improvement

Testing

• New integration tests against real Postgres and Redis (reporting-usage-cache.integration.ts, usage-threshold-email.integration.ts). Six of the seven fail on the pre-change code. The Redis-unreachable test goes red if the read deadline is removed
• Covered: a Redis hit skips the sum; a miss sums and stores it with a TTL; a corrupt value is treated as a miss; one email per period across concurrent and repeated completions; 80% then 100%, never the reverse; re-arm next period
• lib/billing and lib/logs/execution unit suites, type-check, lint, and check:audits pass

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
docs	Skipped		Sep 26, 2026 8:18pm UTC

[cubic-dev-ai]

All reported issues were addressed across 8 files

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>

[greptile-apps]

Confidence Score: 5/5

[High risk] Refactors billing usage cache to share reads across processes via Redis.

The PR appears safe to merge; no outstanding findings or new actionable issues were identified.

Summary

The PR shares enterprise reporting-window usage reads through Redis while retaining the local cache and exact ledger fallback. It also makes credits-threshold emails level-triggered and deduplicates them by billing period and limit.

• The latest changes add an indexed claim pre-check and consolidate unsubscribe mocks.
• The previous findings are resolved or were withdrawn.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  A[Usage read] --> B{Local cache hit?}
  B -- Yes --> C[Return cached sum]
  B -- No --> D{Redis hit?}
  D -- Yes --> C
  D -- No --> E[Sum ledger]
  E --> F[Store with Redis NX and TTL]
  E --> C
  G[Completion above threshold] --> H{Claim unclaimed?}
  H -- No --> I[Stop]
  H -- Yes --> J[Resolve eligible recipients]
  J --> K{Atomic claim won?}
  K -- Yes --> L[Send email]
  K -- No --> I

Loading

_{Reviews (4) · Last reviewed commit: "improvement(billing): skip claimed usage..."}

[waleedlatif1]

@greptile

[waleedlatif1]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

All reported issues were addressed across 8 files

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>

[waleedlatif1]

@greptile

[waleedlatif1]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

No issues found across 8 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Re-trigger cubic}

[waleedlatif1]

@greptile

[waleedlatif1]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

All reported issues were addressed across 12 files

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>