[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-mongodb-atlas-admin-openapi-2026-06-15-remove-effectivewaveassignment-and-waveassignment-fields":3},{"source":4,"alert":11},{"id":5,"displayName":6,"vendor":7,"kind":8,"apiType":9,"url":10},"mongodb-atlas-admin-openapi","MongoDB Atlas Admin API","mongodb","openapi-json","rest","https:\u002F\u002Fraw.githubusercontent.com\u002Fmongodb\u002Fopenapi\u002Fmain\u002Fopenapi\u002Fv2.json",{"id":12,"slug":13,"severity":14,"title":15,"summary":16,"detectedAt":17},"01KV63N942VAPQXB8MXBXB21KY","2026-06-15-remove-effectivewaveassignment-and-waveassignment-fields","Breaking","Remove effectiveWaveAssignment and waveAssignment fields from maintenance window","The `effectiveWaveAssignment` (read-only) and `waveAssignment` (writable) fields have been removed from the maintenance window schema. Clients that read `effectiveWaveAssignment` or write `waveAssignment` to control cross-organization maintenance sequencing will break — the writable field removal is especially impactful as there is no longer a documented way to set a manual wave assignment.","2026-06-15T17:00:55.810Z"]