Copy Jobs — Copy Job Active Queue Management
The Copy Job Active Queue Management sub-tab shows all copy jobs currently in the dispatch queue. These are jobs that are:
- Pending dispatch
- Actively running
- Auto-paused under a 503 holdoff
- Waiting for an agent to reconnect
Capacity Bar
The color-coded bar at the top reads Running: N / M · X queued.
| Value | Meaning |
|---|---|
| N | The number of actively running jobs. |
| M | The total slot capacity across online agents. |
| X | The number of jobs still waiting in pending. Pending jobs do not count toward the running percentage. |
The bar color shows the state of the pool:
| Color | Meaning |
|---|---|
| Green | There is headroom. |
| Amber | Running jobs are at 100% of capacity and pending jobs are waiting. |
| Red | One or more agents are in agent_pending_report (offline). |
Pill counts show the totals for running, pending, auto-paused, and offline-agent jobs.
Live Jobs Panel
The Live Jobs panel shows all running, auto-paused, and agent_pending_report jobs. Pending jobs are excluded and appear only in the Queue panel.
Offline agents section
An amber collapsible section at the top groups jobs on offline agents. Each agent has a countdown to the crash-timeout auto-fail. The section has its own checkbox controls for bulk Re-submit and Cancel on the offline rows.
Re-submit rules
- Re-submit is refused with the message "An active agent job already exists for this config…" while another job of the same policy is running on a live copy agent. This includes the selected job itself if it is still running normally. Cancel it first.
- Jobs stuck on an offline agent do not count. You can re-submit stuck Full Copy and Incremental jobs.
- If several stuck jobs belong to one policy, the first one restarts and the others are refused until it finishes.
- Batch Sync jobs are re-submitted as a Batch Sync resume of their remaining windows. This is refused while any job of the policy is still active, so cancel a stuck Batch Sync job first.
Failure column
The Failure column appears between Status and Copy Engine. It shows why a job failed as a readable label.
| Label | Meaning |
|---|---|
| Canceled | An operator canceled the job. |
| Watchdog: never started | The job stayed pending and was never picked up. |
| Watchdog: timeout | The job's agent went offline or stopped reporting and did not come back in time. |
| Watchdog: re-queued | The watchdog re-queued a pending job because its assigned agent went offline. The job continues. This is not a failure. |
| Engine error | The agent reported an engine failure. |
| Ransomware Event | The ransomware-detection gate blocked or canceled the job. |
| No copy agent | The job failed before it started because no copy agent could take it. Either no agent was online and undrained (Auto), or the one agent the job was pinned to was offline. The job's error says which. |
Failed jobs leave the live view, so you usually see No copy agent only when you look up a job with Find by ID.
Per-agent summary strip
A summary strip above the filter bar shows each agent as a blue pill with its name and number of active vault jobs. Click a pill to filter the list to that agent. Click it again to clear the filter.
Queue Panel
The Queue panel is a tab within Copy Job Active Queue Management. It shows only pending jobs that are waiting to be dispatched.
A green flash animation plays when a job moves from pending to running. This confirms that an agent picked up the job.
Priority
Jobs are dispatched in priority order: CRITICAL, then HIGH, NORMAL, and LOW. Within the same tier, the oldest job runs first.
| Tier | Meaning |
|---|---|
| CRITICAL | Runs before everything else. |
| HIGH | Urgent. Does not preempt jobs that are already running. |
| NORMAL | The default for all new copy jobs. |
| LOW | Background priority. Runs only when no higher-priority work is waiting. |
Bulk Operations
Select jobs with the checkboxes and use the bulk action bar to change priority, cancel, or re-submit (resume) the selected jobs at once.
While the Incremental Sync switch is off (Cyber Vault > Incremental Sync > Settings), incremental and Batch Sync jobs cannot be re-submitted. They are skipped and listed as "skipped — incremental sync is disabled". The button is grayed out when only such jobs are selected. Full copies are not affected.
Select All
Select All works in two phases. The first header-checkbox click selects all loaded rows and shows a Select all N link in the banner.
Click the link to fetch every matching job ID from the server and select them all. Bulk actions then apply to every match, even rows that are not currently visible.
Find by ID
The Find by ID input on both the Live Jobs and Queue tabs accepts comma-separated job IDs, for example 17304, 16567, 16528. It performs a debounced lookup that bypasses pagination and the active-jobs filter.
The result includes completed and failed jobs as well as live ones. A blue banner reports how many of the requested IDs were found.
Normal filters are suppressed while ID search is active. Clear the field or switch tabs to return to normal mode.
Auto-Refresh
The page polls every 30 seconds. A countdown next to the Refresh button shows the seconds remaining.
Tips
Use the agent filter to spot load imbalance. If one agent has a much deeper queue than the others, start bulk syncs with Run on: Auto and use bulk resume. The Auto Distribution Plan shown before the jobs start spreads them across the online copy agents.
Promote a stalled job to CRITICAL to force it to the front of its assigned agent's queue on the next poll.
Auto-paused jobs are listed alongside running jobs in Live Jobs. A job is auto-paused when it hits an HTTP 503 throttle holdoff. One 503 from the source or target pauses all jobs on that copy agent for 30 seconds to 5 minutes. Use the Status filter to show only Auto-Paused jobs.