New: MCP server monitoring is live. Start free trial
CloudflareSchemaBehavioral

Response schema changed for GET /accounts/{account_id}/workers/dispatch/namespaces/{dispatch_namespace}/scripts/{script_name}/settings (workers_export_config)

Affected surface
GET /accounts/{account_id}/workers/dispatch/namespaces/{dispatch_namespace}/scripts/{script_name}/settings
Affected field
workers_export_config

What changed

Response schema changed for GET /accounts/{account_id}/workers/dispatch/namespaces/{dispatch_namespace}/scripts/{script_name}/settings (workers_export_config) Affected surface: GET /accounts/{account_id}/workers/dispatch/namespaces/{dispatch_namespace}/scripts/{script_name}/settings. Root cause: schema `workers_export_config`. Detected at Sun, 26 Jul 2026 09:26:56 UTC UTC.

Diff

{
  "path": "GET /accounts/{account_id}/workers/dispatch/namespaces/{dispatch_namespace}/scripts/{script_name}/settings",
  "removed_fields": [
    "cache",
    "type"
  ],
  "schema_path": "schema workers_export_config"
}

Likely impact

The contract still holds, but observable behavior shifted — defaults, response timing, or rate-limit shaping. Existing code keeps compiling and most calls keep working, but edge cases may differ. Worth a sanity check.

Diff your serializers against the new schema. The diff above shows what moved.

Catch changes like this on every API you depend on.

Intello monitors 100+ APIs and tells you the moment something changes — before it breaks production.