orke package retry
Request immediate progress from an observed retry or schedule wait.
When to use it
Request immediate progress from an observed retry or schedule wait.
Usage
Syntax · [ ] marks optional arguments
orke package retry --slug <string> --runId <string> [--cycleId <string>] [--stepIndex <integer>] --waitRevision <integer> --phase <runningStep|retryWaiting|scheduleWaiting|decisionWaiting>Options
| Options | Required? | Value and description |
|---|---|---|
--slug | Required | Package identifier returned by list or create. |
--runId | Required | Run ID observed in status. |
--cycleId | Optional | Cycle ID to query, or the observed current cycle ID. |
--stepIndex | Optional | Observed current step index. Range: 1–2147483647 |
--waitRevision | Required | Wait state revision from the status response. Range: 0 or greater (check the command-specific upper limit) |
--phase | Required | runningStep | retryWaiting | scheduleWaiting | decisionWaitingCurrently observed execution phase. |
Common management options and errors →
Example
Terminal
orke package retry --slug package_slug --runId observed_runId --cycleId observed_cycleId --stepIndex 1 --waitRevision 0 --phase retryWaitingReplace the example IDs, folders, references, and revision with values from actual queries. Element references such as e7 must also come from the latest observation.
What to check in the result
PackageDescriptor: definition/revision/readError, runtime/target/allowedActions, completedStages/attention/recovery
Behavior and states to watch
- Take runId, cycleId, stepIndex, waitRevision, and phase from the observed target in the same status response. Replace the example step index 1 and revision 0 with the actual values too. Omit cycleId or stepIndex only when that field is null in the observation. The server does not fill omitted values from the current run, so a different target is rejected with package_conflict.
- Check data, error, and completedStages in partial results.
- Supported observed phases:
retryWaiting,scheduleWaiting.