Tasks

Every action NetDefense takes on a device becomes a task — sync, restart, ping, plugin install, backup. Tasks are the audit trail and the debugging surface. The Tasks page lists every task in the active organization; clicking one opens its detail page.

Tasks list

Each row is one task. The columns:

Column	Meaning
Task Code	Short opaque identifier. Click to open the task.
Type	SYNC, RESTART, PING, PULL, PUSH, BACKUP, PLUGIN_INSTALL, etc.
Status	PENDING (waiting to run), IN_PROGRESS, COMPLETED, FAILED, or EXPIRED (the device never came back online before the task’s expiry).
Device	The device the task ran against (or the special __deleted__ suffix for devices removed mid-task).
Organization	Always the active one.
Scheduled	When a deferred task is set to fire; — for immediate tasks.
Created	When the task was added to the queue.

The filter bar above the table accepts a device-name substring, a type dropdown, and a status dropdown.

Auto-refresh ON (top-right) keeps the list live — useful when you’re watching a fan-out (e.g. sync on the whole organization) progress.

Task detail

The header shows the task code and a colour-coded status badge. Below it, four cards:

Task Information — task code, type, status, target device, and organization. Timestamps — when the task was created and last updated, when it was scheduled to fire (Immediate if it ran on dispatch), and when it expires if the device never picks it up. Message — the agent’s result string. For a successful restart this is something like Agent restart scheduled via rc.d; for failures it’s the underlying error message — start here when debugging. Actions — task-level operations. Refresh re-fetches the task to show updated state without reloading the page. Long-running tasks may also expose a Cancel action while they’re still PENDING.

Tasks are immutable after they finish — you can’t edit history. If a task failed and you want to retry, use the action that created it (re-sync, re-run, etc.) to issue a fresh task.