Configure Runtime input for a Job target
For a Job target, use the expanded Options section at the bottom of the Schedule editor. Enter a JSON object in Runtime input, using the same editor as Job templates, and select Override, Deep Override or Replace from the dropdown with icons and descriptions.
Override is shallow: nested objects and arrays replace the value at their top-level key rather than merging recursively. Values such as
false, 0, and null inside the object are retained. The root must be an object; arrays, strings, numbers, and null are rejected.
Use Deep Override to change part of a nested configuration. For example, Job defaults { "export": { "format": "csv", "encoding": "utf8" } } and automation input { "export": { "format": "xlsx" } } produce { "export": { "format": "xlsx", "encoding": "utf8" } }. An empty nested object preserves existing nested values; a change of value type replaces the whole value. Arrays are never concatenated, and null does not delete a field. Existing Override and Replace behavior is unchanged.
The Component reads the resolved object through api.input('templateInputs'). These settings apply to both cron occurrences and manual Run. They do not change the Job template’s execution policy, concurrency, or retry settings, and do not configure Agent or Materialized View targets.
The Platform API uses inputMode: "override" for Override, inputMode: "deep_override" for Deep Override and inputMode: "replace" for Replace, matching the UI. Existing definitions are migrated without changing their effective behavior.
New definitions use input: {} and inputMode: "override" by default, preserving Job defaults. API updates retain stored fields when those fields are omitted. Send both fields to return to the defaults.
One export Job, two cadences
Keep one price-list export Job template with Runtime input:
Both keep
region: "eu" and share the template’s Component, principal, concurrency, and retry policy. The Component selects the export path from api.input('templateInputs').full.
An accepted occurrence retains its Runtime input and mode. Later Schedule edits affect subsequent occurrences, not Jobs already queued or running or their retry attempts.
Continue with schedules.