Copy Job Queue

The Copy Job Queue page provides a real-time view of all copy engine job activity. It shows running jobs, jobs waiting to be dispatched, jobs auto-paused under a 503 holdoff, and the current capacity across all copy agents.

The page refreshes automatically every 30 seconds. A countdown timer next to the Refresh button shows the time until the next refresh.

Overview

Copy jobs are dispatched to copy agents, which are the processes that perform the actual data transfer. Each job is assigned to a specific agent when it is submitted.

The queue page shows the full picture: how many agents are online, which jobs are consuming capacity, and which jobs are waiting. You can also change job priorities and perform bulk operations from this page.

Live Jobs Tab

The Live Jobs tab shows all jobs in the running, auto-paused, or agent_pending_report state. Pending jobs are excluded and appear only in the Queue tab.

Capacity bar

The capacity bar 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 pending jobs waiting to be dispatched. Pending jobs do not count toward the running percentage.

The bar color shows the state of the pool:

Color	Meaning
Green	Capacity is healthy.
Amber	Running jobs are at 100% of capacity and one or more jobs are still queued.
Red	One or more agents are in agent_pending_report (offline).

Pill counters next to the bar show the exact number of running, pending, auto-paused, and offline-agent jobs.

Offline agents section

If any agents have not reported in recently, they appear in an amber collapsible section. Each offline agent shows a countdown timer. The timer shows how long remains before the system automatically fails the jobs assigned to that agent, based on the crash timeout setting.

Each offline row has its own checkbox. The section header includes Select All, Re-submit Selected, and Cancel Selected buttons. These buttons act on the offline rows independently of the selection in the main table.

Per-agent summary strip

Above the filter bar, a row of blue pills shows each agent's current number of active vault jobs. Click a pill to filter the list to that agent. Click it again to clear the filter.

Failure column

The Failure column sits between Status and Copy Engine. It shows why a job failed as a badge.

Badge	Meaning
Canceled	An operator canceled the job.
Watchdog: never started	The job stayed pending and was never picked up.
Watchdog: timeout	The agent went offline or stopped reporting and did not come back in time.
Watchdog: re-queued	A pending job was re-queued because its agent went offline. The job continues. This is not a failure.
Engine error	The copy agent reported an error.
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 the No copy agent badge only when you look up a job with Find by ID.

Filters

You can filter the job list by:

• Status (running, pending, auto-paused, or agent_pending_report)
• Priority tier
• Agent name
• Configuration name (search)

Filters can be combined.

The Find by ID input accepts comma-separated job IDs, for example 17304, 16567. It performs a debounced lookup by job ID that bypasses pagination and the active-jobs filter. Results can include completed or failed jobs as well as live ones.

Click the × in the field, or switch tabs, to return to normal mode.

Multi-select and bulk actions

The checkbox on each row enables these bulk actions:

• Priority change
• Cancel
• Re-submit Selected (resume)

Re-submit routes failed or canceled Full Copy, Incremental, and Batch Sync jobs through their respective resume paths.

Select All works in two phases. The first click selects only the loaded rows and shows a Select all N link in the banner. Click the link to fetch every matching job ID from the server. The bulk action then applies to every match, including rows that are not on the current page.

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.

info

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.

Queue Tab

The Queue tab shows only pending jobs that are waiting to be dispatched to an agent. Each job is assigned to a specific agent when it is submitted, so each row shows which agent the job is waiting for.

When an agent finishes its current job and picks up a pending one, a green dispatch animation plays on the row to confirm the transition. The row briefly bursts upward with a green glow, slides back in as Running, holds for a few seconds, and then fades out.

Priority Tiers

Jobs run in priority order within each agent. When two jobs have the same priority, the older job runs first.

Tier	Value	Use
CRITICAL	40	Highest priority. Use for urgent transfers that must run before everything else. Overrides all other queued jobs for the assigned agent.
HIGH	30	Elevated priority for urgent but non-blocking transfers.
NORMAL	20	The default priority for all newly submitted copy jobs.
LOW	10	Background priority. These jobs run only when no higher-priority jobs are queued for the agent.

Workflows

Change the priority of a pending job

1. Locate the job in the Live Jobs tab using the search or status filter.
2. Click the priority badge on the job row to open the priority selector.
3. Select the new priority tier.

The change takes effect immediately. The job may move up or down in the queue relative to other pending jobs for the same agent. Priority applies to pending jobs only. You cannot change the priority of a job that is already running.

Bulk-promote pending jobs to HIGH priority

1. Open the Queue tab.
2. Select the checkboxes next to the jobs you want to promote.
3. Click the bulk priority control that appears and select HIGH.

All selected jobs are updated.

Identify which agent is overloaded

1. Open the Live Jobs tab.
2. Use the Agent filter to cycle through the agents and note the running count for each.
3. If one agent has many running and pending jobs while others are idle, check the agent configuration in Cyber Vault > Agent Fleet Management to rebalance.

Tips

tip

The capacity bar reflects total slots across all online agents. An amber bar does not mean all agents are equally loaded. One agent may be saturated while others are idle.

tip

If an agent appears in the offline section, check the host that runs the agent process. The auto-fail countdown is based on the crash timeout configured in Cyber Vault > Agent Fleet Management.

You can re-submit jobs in the offline section with Re-submit Selected before the countdown ends. After a job is auto-failed, it leaves this page. Resume it with ↩ on Copy Jobs - Live View & History. Incremental and Batch Sync jobs can be resumed only while the Incremental Sync switch is on.

tip

The green dispatch animation on the Queue tab only shows that a job moved from pending to running. It does not show whether the copy succeeded.

tip

Priority changes apply immediately to the queue order, but they cannot preempt a job that is already copying.