tofupilot queue

Last updated on June 26, 2026

The queue command manages the offline upload queue. When a station runs offline, completed runs queue locally and upload when connectivity returns, and without a subcommand queue lists queued entries.

list queue
tofupilot queue
tofupilot queue ls

Add the global --json flag to any subcommand for machine-readable output.

get

The get subcommand shows the full detail of a single queued entry: status, attempt count, retry schedule, last error, and attachments.

queue get
tofupilot queue get queue_xyz789

retry

The retry subcommand force-retries every pending upload, or a single entry when given a queue ID. Both forms un-park entries that failed with a deterministic error, and both require authentication. The all-entries form exits non-zero if any entry is still queued after the pass; the single-entry form exits non-zero if that entry's upload fails again. With --json, the single-entry form reports the created run ID on success or the persisted failure record, and the all-entries form reports the remaining queue count.

queue retry
tofupilot queue retry
tofupilot queue retry queue_xyz789

rm

The rm subcommand removes a single queued entry by ID, or every entry with --all. Removal hard-deletes the entry and its on-disk attachments with no recovery.

queue rm
tofupilot queue rm queue_xyz789
tofupilot queue rm --all

export

The export subcommand prints the entry's create-run payload as JSON, or writes it to a file with --out. The payload is the exact request body the queue would send to the create-run API, useful for archiving or debugging before removing an entry. It does not include attachment files, only their queue metadata, and an entry whose run was already created server-side carries a run_id in the queue (visible via queue get) — re-submitting such a payload creates a duplicate run.

queue export
tofupilot queue export queue_xyz789
tofupilot queue export queue_xyz789 --out run.json

How is this guide?

On this page