Skip to content

BA26: Queued job was cancelled

Error code Product Applies to
BA26 BackupAssist For BackupAssist 14.0.0 or later.

Description

BackupAssist runs one backup at a time. If a job is scheduled or started while another job is still running, it is placed in a queue and starts automatically when the running job finishes.

BA26 is recorded when a queued job is cancelled from the Troubleshooting screen before it started. A completed backup report is produced for that run carrying the "Queued job was cancelled" condition, in the same way BackupAssist records a report for a missed backup. It most commonly appears after an administrator clears jobs that were stuck in the queue - typically because an earlier job could not be cancelled and would not finish, so following jobs banked up behind it.

Resolution

If you cancelled the queued job yourself, BA26 is expected and benign - it simply records that the run was cancelled rather than missed or failed. No further action is required.

Resolution 2 - Investigate jobs that repeatedly get stuck in the queue

If jobs bank up in the queue on their own, the cause is usually a job at the head of the queue that will not finish or cancel - for example an engine that has stopped responding, often due to interference from antivirus or security software.

  1. Open BackupAssist and review the running and queued jobs.
  2. Identify the job that will not finish (the one holding up the queue) and stop it; the queued jobs can be cancelled from the Troubleshooting screen.
  3. Check for antivirus or security software that may be holding a backup process open, and add the relevant BackupAssist processes/paths to its exclusions.
  4. If backups regularly hang, generate diagnostics and contact support.

Note on the backup report

The backup report shows: Queued job was cancelled. This is an informational condition recording a cancelled queued run; it does not indicate a backup failure.

Last updated Created Further assistance
7th Aug 2026 7th Aug 2026 BackupAssist Support page