PortivoDocs · v2.0.0Complete handbookportivo.orgGitHub
Operations

Jobs and lifecycle

Execution history, interruption recovery, cancel and retry.

v2.0.0Source-backed

Job structure

A Job represents one operation request and contains per-device Job Items. The UI exposes target count, success/failure state, timestamps and detailed item output while preserving credential secrecy.

Lifecycle

Portivo tracks queued, running, cancelling, cancelled, completed, failed and interrupted states. A startup reconciliation converts orphaned active Jobs from a previous process into interrupted state.

Cancel

Cancellation stops new switch executions at safe item boundaries rather than forging a successful completion state.

Retry

Retry creates a new traceable Job linked to the original rather than rewriting history.

Removal

Terminal Jobs can be removed from Jobs history under authorization, while the corresponding activity evidence remains auditable.

Source-backed detail

Durable execution state

Jobs contain an immutable action snapshot, target scope and per-device Job Items. Running work publishes heartbeat evidence. If the service restarts, persisted Queued, Running or Cancelling work is reconciled to Interrupted; completed target evidence is preserved and only unfinished items are marked interrupted.

Cancel, retry and removal

Cancel is cooperative and records the request before the worker stops at a safe boundary. Retry creates traceable follow-up work for eligible failed or interrupted targets; it does not rewrite the original record. Removal deletes a completed history entry only when policy and permissions allow it and never acts as a substitute for cancelling live work.

Reading results

  • Use target-level status, timestamps and output evidence.
  • Distinguish execution failure from device compatibility rejection.
  • Review pending configuration after successful change actions.
  • Export PDF when a portable operational record is required.