Agent skill · software engineering · jeremylongshore
hex-rate-limits
Implement Hex rate limiting, backoff, and idempotency patterns.
Why this skill is useful
Adds a complete implementation of rate limiting, retry logic, and backoff strategies specifically for the Hex API, which the AI wouldn't generate on its own.
What it needs
Requires hex account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Hex Rate Limits Overview Hex's API enforces tight limits on project run triggers (20 per minute, 60 per hour) while leaving read operations like status checks and project listing largely unthrottled. Data teams scheduling batch analytics runs or triggering parameterized notebooks from CI/CD pipelines must carefully manage the hourly cap, since a single pipeline triggering 15 projects can consume a quarter of the hourly budget. Polling run status is free, but triggering runs is the bottleneck that shapes integration architecture. Rate Limit Reference Endpoint Limit Window Scope ---------- ------- -------- ------- RunProject (trigger) 20 req 1 minute Per API token RunProject (trigger) 60 req 1 hour Per API token GetRunStatus No hard limit - Per API token ListProjects No hard limit - Per API token CancelRun No hard limit - Per API token Rate Limiter Implementation Retry Strategy Batch Processing Error Handling Issue Cause Fix ------- ------- ----- 429 on RunProject Exceeded 20/min or 60/hour trigger limit Queue runs, space 5s apart minimum Run stuck in RUNNING Long-running query or compute timeout Poll up to 30 min, then CancelRun 401 on scheduled run API token rotated Refresh token in CI secrets before batch Empty run output Project has no published outputs Verify project has published cells 409 concurrent run Same project triggered twice Check run status before re-triggering Prerequisites An approved request budget, observed header baseline, and sandbox run workload using opaque project IDs. A bounded queue, idempotency key for mutations, and reviewed recovery path for exhausted work. Instructions 1. Classify requests by project and operation, applying per-scope concurrency limits before dispatch. 2. Honor server retry guidance when available; otherwise use bounded exponential backoff with jitter and a maximum attempt count. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/hex-rate-limits