shipper auto-ship retry-observation
shipper auto-ship retry-observation
Section titled “shipper auto-ship retry-observation”Usage: shipper auto-ship retry-observation
Retry repository observation through the current daemon owner
Arguments
Section titled “Arguments”| Argument | Required | Description | Choices |
|---|---|---|---|
| None | - | - | - |
| Long | Short | Value | Default | Description | Choices |
|---|---|---|---|---|---|
| None | - | - | - | - | - |
Examples
Section titled “Examples”Request observation through the existing repository daemon owner.
shipper auto-ship retry-observationExit Codes
Section titled “Exit Codes”| Code | When |
|---|---|
| 0 | Observation is scheduled or already in progress. |
| 1 | Controls or ownership refuse recovery, or the current daemon is unavailable. |
Constraints
Section titled “Constraints”- Connects only to the current daemon owner. Preserves repository registration, enablement, workers, halt, safety stops, and policy backoff.
- An unfinished inspection coalesces one follow-up; it has no next observation scheduled unless a real time is reported. Acknowledgement does not clear observation health.
- If inspection remains unfinished, run shipper daemon stop, then shipper daemon run only if stop succeeded. Normal stop protects genuine workflow and persistence work across all repositories and identifies blockers. It never forces work to stop.
- Terminal-owned or Desktop fallback observation must be recovered through that host.