TransitionOperationInput
Input for transitioning operation status
Fields
Optional same-transaction input freshness guard for SETUP, RUNNING or RESTARTING commands. Omission preserves existing behavior. Stock checking supports initial whole-work SETUP only; partial/resume stock checks are unsupported.
Optional explicit allocation releases with CANCELLED command and receipt. Each selected allocation must release its entire remaining quantity with current counters. Include all outstanding operation/item allocations; matching job allocations are explicitly selected only. Requires warehouseStock:write. Omission preserves no-warehouse behavior; products and consumed quantities never change.
COMMAND by default; REPORT requires effectiveAt and retains observations even when delayed
Possible values (2)
COMMANDRequest a valid transition of current state; the default
REPORTRecord an observed status at effectiveAt, accepting delayed or completion-only reports without regressing newer state
Explicit allocation from a published scenario to capture at first SETUP. Once bound it cannot be changed; subsequent transitions may omit it.
Atomic retry identity; completion requires actual start/completion times and commits its metrics in the same transaction
Business occurrence time. COMMAND defaults to now and preserves command chronology; REPORT requires this field and accepts delayed observations. Recording time remains current.
When the work actually started, for sources that report a finished operation in one message instead of stepwise updates. Only valid with status COMPLETED; must not be later than effectiveAt. An earlier recorded start is kept.
Operation ID to transition
Target status
Possible values (10)
PENDINGNot yet available for scheduling
AVAILABLEReady to be scheduled
SETUPMachine setup in progress
RUNNINGOperation is running
CLEANUPCleanup/teardown in progress
COMPLETEDSuccessfully completed
FAILEDOperation failed
STOPPEDManually stopped
CANCELLEDOperation cancelled
RESTARTINGRestarting after failure/stop
Referenced by (1)
Exact type SDL
"""Input for transitioning operation status"""
input TransitionOperationInput {
"""
Optional same-transaction input freshness guard for SETUP, RUNNING or RESTARTING commands. Omission preserves existing behavior. Stock checking supports initial whole-work SETUP only; partial/resume stock checks are unsupported.
"""
inputCheck: OperationExecutionInputCheck
"""
Optional explicit allocation releases with CANCELLED command and receipt. Each selected allocation must release its entire remaining quantity with current counters. Include all outstanding operation/item allocations; matching job allocations are explicitly selected only. Requires warehouseStock:write. Omission preserves no-warehouse behavior; products and consumed quantities never change.
"""
materialReleases: [MaterialLotChangeInput!]
"""
COMMAND by default; REPORT requires effectiveAt and retains observations even when delayed
"""
mode: OperationTransitionMode
"""
Explicit allocation from a published scenario to capture at first SETUP. Once bound it cannot be changed; subsequent transitions may omit it.
"""
allocationId: ScheduleAllocationID
"""
Atomic retry identity; completion requires actual start/completion times and commits its metrics in the same transaction
"""
receipt: ReceiptInput
"""
Business occurrence time. COMMAND defaults to now and preserves command chronology; REPORT requires this field and accepts delayed observations. Recording time remains current.
"""
effectiveAt: ISO8601
"""
When the work actually started, for sources that report a finished operation in one message instead of stepwise updates. Only valid with status COMPLETED; must not be later than effectiveAt. An earlier recorded start is kept.
"""
startedAt: ISO8601
"""Operation ID to transition"""
id: OperationID!
"""Target status"""
status: OperationStatus!
}