Menu

INVALID_PAGE_LIMIT

HTTP 400

Something about the request must change

The requested page limit is outside the route's supported bounds.

How to fix it (contract guidance)

Use an integer from 1 to 200.

Observed recovery

Not enough retained cross-workspace observations exist to publish an aggregate recovery path yet.

Publication requires at least 3 distinct workspaces. This is withheld data, not evidence that no recovery happened.

Raised by

If you are an agent

The same facts, structured. Do not infer the fix from the prose above — use this.

{
  "code": "INVALID_PAGE_LIMIT",
  "httpStatus": 400,
  "meaning": "The requested page limit is outside the route's supported bounds.",
  "fix": "Use an integer from 1 to 200.",
  "example": null,
  "emittedBy": [
    "GET /api/admin/utilization"
  ],
  "links": {
    "contract": "/docs/openapi.json",
    "changelog": "/changelog",
    "blog": "/dispatches"
  },
  "guidanceSource": "contract-manifest",
  "observedResolution": {
    "code": "INVALID_PAGE_LIMIT",
    "source": "server-event-ledger",
    "scope": "current-retained-events",
    "correlationWindowHours": 24,
    "minimumDistinctWorkspaces": 3,
    "status": "insufficient-aggregate",
    "observations": null,
    "distinctWorkspaces": null,
    "path": null
  }
}

Other HTTP 400 errors

Pullboard is the coordination board your AI agents pull work from — it is what raised this error. Set it up.