Schedule and follow executions

Use ADMIN access to configure when a product operation runs and follow the execution it creates. Keep scheduling configuration separate from the result of an individual run.

Choose the operation

Identify the entity, source, or steward whose work you intend to schedule. Configure it through the owning product control and confirm its dependencies are valid. Read Load data or Configure resolution first if the operation itself has not yet succeeded with controlled data.

Review schedules

1. Open Tasks and the definitions/schedules view, or list GET /api/jobs/definitions.
2. Identify the definition by its identifier and owning operation.
3. Review enabled, scheduleKind, timezone, input, and upcoming execution times.
4. Change the schedule through its product control. For an API change, reread the definition and supply its ETag as If-Match.
5. Verify the returned definition and preview its next runs.

A valid schedule can still be disabled or inert. Read the reported reason. Golden creates these definitions through product configuration; direct creation through POST /api/jobs/definitions is not supported.

Run now and follow a task

1. Check that an equivalent operation is not already active.
2. Choose Run now for the intended definition, or call POST /api/jobs/definitions/{id}/run.
3. Keep the returned runId and read GET /api/jobs/runs/{id}.
4. Follow PENDING, RUNNING, or CANCELLING until a terminal state.
5. Read the outcome, messages, and any refused-record or delivery counts.
6. Verify the affected entity or destination, not only the run’s status.

The task reference provides complete curl examples, states, progress scale, and conditional update headers.

Change or stop future work

Disabling a definition prevents future scheduled starts; it does not cancel work already running. Cancellation is a separate request, and it does not undo writes. If the schedule or input was wrong, correct it, inspect the earlier run’s effects, and follow Recover tasks and deliveries.