Skip to content

Raise free-tier execution rate limit to 10k/hour #1931

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.

Sign up for GitHub

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

Merged
RhysSullivan merged 1 commit into from
Sep 3, 2026
Merged

Raise free-tier execution rate limit to 10k/hour #1931

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion apps/cloud/src/engine/execution-rate-limit.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ export const RATE_LIMIT_WINDOW_MS = 3_600_000;
// against the largest customer is a losing game, so the number no longer tries
// to describe them — paid orgs are exempt below, and this now has only
// free-tier abuse to cover, which is what it was picked for.
export const EXECUTIONS_PER_ORG_PER_HOUR = 1000;
export const EXECUTIONS_PER_ORG_PER_HOUR = 10_000;
// Counter DO slower than this => fail open rather than stall executions.
const RATE_LIMIT_CHECK_TIMEOUT_MS = 2_000;
// Exemption lookup slower than this => treat as unresolved.
Expand Down
2 changes: 1 addition & 1 deletion e2e/setup/execution-limits.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
//
// Picking the value is a squeeze from both sides. It must be LOW enough that
// the backstop scenario can exhaust it with real sequential executions (prod's
// 1000/hour cannot be reached in a test), and HIGH enough that no other
// 10,000/hour cannot be reached in a test), and HIGH enough that no other
// scenario trips it: the counter is per organization and every `execute` a
// scenario runs counts against its org, so this must exceed the busiest
// single-org scenario's execute count (currently toolkits-mcp at ~8) with
Expand Down
Loading