Same symptom here, and I can add evidence that isolates it to the Console's schema backend rather than to my project or my schema.
Container: iCloud.com.zx.PatternMaking
Team ID: T8B35NA44M
Platform: CloudKit Console (web), Safari + Chrome, also in Private Browsing
First seen: 2026-10-11. Last successful promotion to Production: 2026-09-18.
WHAT FAILS (both Development and Production environments)
- Schema -> Indexes / Record Types / Security Roles: "Internal error". Record Types intermittently renders but shows "No record types found".
- Settings -> Tokens & Keys: "Error fetching API tokens / Internal error". (The account-level Settings -> Tokens panel works fine, so the failure is scoped to this container.)
- Deploy Schema Changes... -> "Confirm Deployment": BOTH the "Changes" tab and the "Diff View" tab show "Internal error", and "Deploy" is disabled.
WHAT WORKS (same team, same account, same browser)
- All of Data -> Records / Zones / Subscriptions.
- Another container, iCloud.com.zx.GradientWallpaper, is fully functional, including its schema pages and deployment.
- The CloudKit Web Services API via cktool, for THIS container:
cktool export-schema --environment development-> 6 record typescktool export-schema --environment production-> 3 record types Both files are byte-for-byte identical (same SHA-256) to the files produced by the Console's own "Export Schema...", so the stored schema is intact, readable and well-formed. This is not a corrupt-schema problem.
THE PENDING CHANGE IS PURELY ADDITIVE Field-by-field diff of the two exports, including index flags:
- present in Production but missing from Development: 0
- additions: 5 fields on CD_CanvasItem plus 3 whole record types.
Nothing removed, retyped or renamed, so it satisfies the CloudKit rule that production schema changes may only add. The Console fails before it can even compute the diff.
THERE IS NO NON-CONSOLE PATH TO PROMOTE
cktool import-schema --environment production and
cktool validate-schema --environment production both fail with:
"The request was not allowed: BadRequestException: endpoint not applicable
in the environment 'production'"
and cktool has no promote/deploy subcommand. So the one and only way to
promote a schema - the Console - is exactly the thing that is broken.
SERVER LOGS SHOW ZERO SERVER-SIDE ERRORS Console -> Logs export for 2026-10-07 .. 2026-10-11 UTC, 181 events: 176/181 SUCCESS, no server errors at all. The only 5 failures are USER_ERROR/BAD_REQUEST RecordQuery calls issued by the Console itself (interfaceType=WEB) on 10-07. The schema/management surface writes no entries to this log, which is consistent with the failure being isolated there.
I'd be grateful for any workaround, or for someone from Apple to promote the Development schema of this container to Production on my behalf - the change is purely additive and I'm blocked from shipping.
I have filed a feedback report. The report id is FB25146476.