[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-datadog-v2-openapi-2026-05-28-historical-job-api-id-field-removed-new-fields-added-to":3},{"source":4,"alert":11},{"id":5,"displayName":6,"vendor":7,"kind":8,"apiType":9,"url":10},"datadog-v2-openapi","Datadog API v2","datadog","openapi-yaml","rest","https:\u002F\u002Fraw.githubusercontent.com\u002FDataDog\u002Fdatadog-api-client-typescript\u002Fmaster\u002F.generator\u002Fschemas\u002Fv2\u002Fopenapi.yaml",{"id":12,"slug":13,"severity":14,"title":15,"summary":16,"detectedAt":17},"01KSR2SPB76HX6C6W91W0FM9R6","2026-05-28-historical-job-api-id-field-removed-new-fields-added-to","Breaking","Historical Job API: id field removed, new fields added to multiple schemas","The `id` field has been **removed** from both `ConvertJobResultsToSignalsAttributes` and `RunHistoricalJobRequest` — clients sending or reading `id` in these request bodies will no longer have this field recognized or returned. Additionally, several new optional fields are added across `HistoricalJobQuery` (`additionalFilters`, `correlatedByFields`, `correlatedQueryIndex`, `customQueryExtension`, `datasetIds`, `index`, `indexes`, `queryLanguage`), `HistoricalJobResponse` (`progressRate`), and `JobDefinitionFromRule` (`caseIndex`), along with `maxItems: 10` constraints on `cases`, `queries`, and `thirdPartyCases` arrays in `JobDefinition`.","2026-05-28T20:00:47.975Z"]