Historical Job API: id field removed, new fields added to multiple schemas
BreakingBreaking change
This is a breaking change — integrations that rely on the affected behaviour will need updates before the change rolls out.
What changed
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.