invocationId and jobDefinitionId added as required fields
BreakingBreaking change
This is a breaking change — integrations that rely on the affected behaviour will need updates before the change rolls out.
What changed
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.