[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-vercel-changelog-2026-05-25-invocationid-and-jobdefinitionid-added-as-required-fields":3},{"source":4,"alert":11},{"id":5,"displayName":6,"vendor":7,"kind":8,"apiType":9,"url":10},"vercel-changelog","Vercel API","vercel","openapi-json","rest","https:\u002F\u002Fopenapi.vercel.sh\u002F",{"id":12,"slug":13,"severity":14,"title":15,"summary":16,"detectedAt":17},"01KSER35GK3EEQ5ES5HYXVWVXA","2026-05-25-invocationid-and-jobdefinitionid-added-as-required-fields","Breaking","invocationId and jobDefinitionId added as required fields","Two new fields, **`invocationId`** and **`jobDefinitionId`**, have been added to a `config`-subKind object schema and listed in its `required` array across five separate schema locations. Because these fields are marked `required`, any client submitting a request body that matches this schema without providing both fields will now fail validation — making this a potentially breaking change for existing integrations.","2026-05-25T05:00:34.195Z"]