Skip to main content
GPU stages are scheduled fairly across accounts, so per-account in-flight caps apply:
  • In-flight jobs per account: template pages note any per-template caps (GPU-heavy stages like matting cap at 3 concurrent per account).
  • At the cap, new runs return the typed blocker IN_FLIGHT at estimate time, or HTTP 429 at run time. Back off and retry; don’t tight-loop.
  • Queue position and estimated wait are reported on the job while queued.
Higher limits for production workloads: contact us: the caps are policy, not physics.