Runway Concurrency and Quota Control

Overview

Runway generation capacity is governed by usage-tier limits, not a universal requests-per-minute number. The application must distinguish accepted-but-queued THROTTLED tasks from create requests rejected with 429, then apply local admission control to protect deadlines and budget.

Prerequisites

• Current organization tier and per-model limit evidence
• Task creation, state, latency, daily-generation, and credit metrics
• A durable queue with priority, deadline, and cancellation policy

Instructions

Step 1: Read live authority

Review the organization Usage page and current tiers documentation. Record per-model concurrency, rolling 24-hour generation cap, 30-day spend cap, and any approved enterprise exception.

Step 2: Measure by model