Skip to content
CortexDocs

Set Gateway rate limits

Create, edit or disable Organization, Team and Member requests-per-minute limits, then verify the affected Gateway path.

Before you begin

Required

  • Organization Admin access

    Use the organization's Admin role and live records. Sample records do not permit writes.

  • Enabled Gateway path

    Wait for Gateway status to load and confirm Gateway is enabled before selecting Create rate limit.

Review organization RPM limits and active statusOpen in Cortex
  • The form supports requests-per-minute limits for Organization, Team and Member scopes.
  • It does not expose token throughput, parallelism, model or provider filters.
  • Unsupported records can appear in the list without being editable.
  • Use Manage budgets for monetary limits and Restrict model/provider access for scoped denies.

Create a requests-per-minute limit

  1. Open Access & limits → Rate Limits for the intended organization and select Create rate limit.
  2. Choose Organization, Team or Member under Applies to. For Team or Member, select the directory subject.
  3. Enter a positive whole number in Limit per minute, then select Create rate limit.
  4. Confirm the subject, RPM value and active status.
Set an organization requests-per-minute limitOpen in Cortex

Change or disable a limit

  1. Select Edit on a supported Organization, Team or Member RPM record.
  2. Change Limit per minute or Status, then select Save changes.
  3. Confirm the refreshed row.

To disable directly, select Disable on the row, confirm in the dialog and check that the retained row is disabled.

Verify the affected path

  • Allow enrolled devices to refresh their configuration before testing a change.
  • A saved active row confirms configuration. Enforcement: Not reported leaves application unconfirmed.
  • Use a controlled request-path test to verify delivery and an applicable HTTP 429 refusal.
  • Recent denial counts are separate from the current counting window.
  • Telemetry is best effort. Empty history does not prove admission.
  • A failure to check the request count can allow traffic to continue despite a configured rate limit. See Policy and enforcement boundaries.
  • Use retry timing or reset headers only when the deployed response supplies them.

Troubleshooting

SymptomNext action
Create rate limit is disabledCheck Admin access, live records and Gateway status.
Limit rejectedEnter a positive whole number.
Edit is disabledCheck for a supported Organization, Team or Member RPM record; listed TPM or parallelism values do not establish edit support.
Stale record on saveRefresh, review the latest configuration and reopen Edit.
HTTP 429 after disablingVerify configuration delivery and identify the refusing resource in Troubleshoot refusals.