Skip to content
Weaver Docs

Queue And History

The left navigation has six working pages. This guide walks each one, with the actions it offers and what to look at when something stalls.

Queue

Section titled “Queue”

Queue is the root route: every active and paused job, with search by name, filters for status, priority, and category, and a table or compact layout. The header holds Pause All, Resume All, the speed limit, and Upload.

Per row: pause, resume, cancel, inline priority and category changes, and a link to Job Detail. Select several rows for Edit Selected, Pause Selected, or Cancel Selected. Cancelling stops a download for good.

Banners across the top explain a held queue: Downloads paused, ISP cap reached with its reset time, Server quota on every eligible server, or No servers. Each links to the setting that clears it.

Upload

Section titled “Upload”

Upload NZB accepts one or more .nzb or .nzb.xz files by drag or browse. Shared settings apply to every staged file: an optional password, Priority of Low, Normal, or High, a category or No category, and Duplicate Handling with a mode, key, and score for clients that group candidates. Files stage first, then submit. A staged file that sits too long expires and must be re-added.

Job Detail

Section titled “Job Detail”

Open any queue or history row. The page shows downloaded and total size, progress, Saved bandwidth from articles Weaver did not need to fetch, speed, output files, metadata such as the original title and duplicate decision, and the Event Log with every pipeline stage and script result.

Actions depend on state: pause, resume, or cancel an active job. For a finished job, Reprocess re-runs the post-download stages without downloading again, Re-download fetches the stored NZB again under the same job, Re-run scripts repeats the post-processing list, and Delete removes the record with an option to delete the downloaded files.

History

Section titled “History”

History lists complete and failed jobs with a name filter and All, Completed, and Failed tabs. Delete one row, the selected rows, or Delete All, each with Also delete downloaded files from disk. Reprocess and re-download are available per row. Deleting history needs Admin scope over the API.

Monitoring

Section titled “Monitoring”

Monitoring shows the pipeline state as tiles, then trends over a range from 10 minutes to 30 days:

  • Pipeline State: active and queued jobs, download speed, and the download, decode, commit, and recovery queue depths.
  • Bandwidth Cap: window usage, limit, and reset.
  • News Servers: each server’s tier, connections in use, and latency.
  • Charts for throughput, download speed, segments, queue depths, active workers, write buffer, and disk write latency, plus jobs by status and free disk space.

Read it before assuming a job is stuck. A growing commit queue or write buffer means the disk is behind. Empty download queues with active jobs mean the servers are.

Logs

Section titled “Logs”

Logs streams the service log with pause, resume, and a text filter. Pause live mode during a burst, filter by a job name or server host, and compare timestamps with Job Detail’s event log. Before sharing logs, check them for hostnames, paths, and usernames.

System Info

Section titled “System Info”

System Info reports the version, uptime, deployment kind, operating system, architecture, and database engine, then compute, memory, and container limits, the storage class and filesystem behind the primary path with a startup random-read benchmark, and capacity for every configured directory. It is the first page to screenshot in a bug report, and where you confirm a version after upgrading.

Section titled “Related”