container.tracking.stopped

Overview

Fired when tracking for a container has been stopped — either because the container lifecycle is complete (e.g. empty returned) or because the container was manually archived by a user.

When This Event Fires

This event fires in two scenarios:

1. Automated completion: The report processing pipeline determines that the container's workflow is complete (e.g. the container has reached EMPTY_RETURNED and the tracking lifecycle is finished). The completionReason in the changes object indicates why tracking stopped.
2. Manual completion: A user manually archives or completes the container from the OpenTrack UI or API.

Payload Structure

{
  "event": "container.tracking.stopped",
  "data": { /* IContainerVoyageResponse — full container snapshot */ },
  "changes": {
    "completionReason": {
      "previous": null,
      "current": "LIFECYCLE_COMPLETE"
    }
  },
  "deliveryAttempt": 1,
  "pendingRetries": 4,
  "sentAt": "2025-07-19T17:00:00.654Z"
}

data object

The full final state of the container at the time tracking was stopped.

changes object

Contains the completionReason with { previous, current }:

• previous is typically null (the container was actively tracked)
• current contains the reason tracking was stopped (e.g. LIFECYCLE_COMPLETE, MANUALLY_ARCHIVED, etc.)

Common Use Cases