Stay within local processing limits

A safety budget was reached; no partial automatic repair is produced.

Match the finding

These titles and messages come from this local checker. They are not AWS service error quotes.

Cause and scope

This checker limits files and output to 1 MiB, nesting to 64 levels, keys and values to 50,000, strings to 262,144 characters, findings to 300, and repair copies to 100. Reference traversal and expansion have additional guarded checks. These are tool limits, not AWS quotas.

What to do

Address already reported issues, or create a smaller complete definition using a trusted local workflow. Keep all necessary schemas, references, routes, and security. Larger definitions may need another local tool.

  1. Read which budget the finding identifies: input size, nesting, nodes, strings, diagnostics, traversal, patches, or output expansion.
  2. For a diagnostic cap, correct the shown findings and rerun to reveal the remaining ones.
  3. For structural or output budgets, review a smaller complete scope or use tooling suited to the complete document. Validate the full final API separately.

Diagnostic illustration: one byte beyond the local input limit

# File measurements, not fields to add to your OpenAPI document.
inputBytes: 1048577
checkerLimitBytes: 1048576
finding: Document exceeds the 1 MiB local processing limit.

A file with this UTF-8 byte length is rejected before OpenAPI analysis. Being within the byte limit does not guarantee that nesting, node, or other budgets pass. Preserve the complete definition and use suitable local tooling rather than truncating it.

Avoid a misleading fix

Do not remove security, truncate strings, drop operations, or weaken schemas merely to fit a budget. Splitting a definition must not leave unresolved references or hide errors in omitted sections.

Check your complete file locally

Choose one OpenAPI 3.0 JSON or YAML file, diagnose the findings, and review any eligible security-copy preview before downloading. No file upload or account is needed.

Open the free OpenAPI checker →

Related findings

Sources and scope

Scope: this local checker, API Gateway REST APIs, and OpenAPI 3.0. Guidance reviewed 4 October 2026. A passing check does not guarantee import or runtime behavior.