Tracking Deployments: Active & History

Every time you push a deployment package to machines, Athena records it as an execution. The console gives you two screens to follow it: Active Deployments, a live board of everything that is scheduled, waiting, or running, and Deployment History, a log of every finished execution where you can open each machine and each package step and read its exit code and output. This page covers both screens, who can use them, how to clean up history, and how to get the same results over the REST API.

Getting there#

Both screens are reached from the Deployments area of the console:

• The Active Deployments (“Monitor running deployments”) and Deployment History (“View past deployment results”) cards on the Deployments page.
• The status counters at the top of the Deployments page: clicking the Running or Pending counter opens Active Deployments; clicking Completed or Failed opens Deployment History.
• The Open queue link on the Dashboard’s Deployments in Flight panel opens Active Deployments.
• When you start a deployment, the console takes you straight to that execution on the Active Deployments screen.

Each screen and each execution also has its own address, so you can bookmark or share a link:

Who can see and do what#

See Permission Model & Role Bundles for how these are granted through roles.

Active Deployments (live board)#

The Active Deployments screen (eyebrow Live Operations) lists every execution that has not finished yet: Running, Pending, and Scheduled, newest first. A legend at the top shows the colour for each of the three states. When nothing is in progress you see No Active Deployments.

Each execution appears as a card showing:

The board updates itself: it listens for live deployment progress, step-completed, and result events from the server, so you do not need to reload the page. Updates come only through that live connection — the board does not poll on a timer. If the connection drops or cannot be opened, the board keeps its current data and shows a Live updates paused – reconnecting badge beside its title while it retries; once reconnected it re-reads the board once and the badge clears. See Live updates paused.

Start and cancel#

Users with deployments.manage see action buttons on each card and in the detail view:

• Start — on a Pending or Scheduled execution, dispatches it now instead of waiting. If the server’s license does not currently allow new work, Start is refused with an error message and the execution stays Pending, so it can be started once the license is renewed (see Licensing).
• Cancel — on a Pending, Scheduled, or Running execution, closes it with status Cancelled, stamps the completion time, and moves it to Deployment History. Cancel ends the execution on the server; it does not send an abort to machines, so a step that a machine has already begun is not interrupted there.

Execution detail: the agent × step matrix#

Click a card to open its live detail view. It has three parts:

• Execution Info — package, start time, total agents, overall progress, and counts of machines Completed, Running, and Failed.
• Agent Step Matrix — one row per machine, one column per package step, and a final status column for that machine. Until the first machine reports, the matrix shows Waiting for agents…. On wide packages the matrix scrolls sideways inside its panel.
• Step output — click any cell in the matrix to open that machine’s result for that step: status, Exit Code, Started At, Completed At, and any Output, Error Output, or Error Message. Click the same cell again, or the close button, to hide it.

Matrix cells use these symbols; hovering a cell shows the step name, its status, and the exit code (or the reason a step was skipped):

The View History button in the detail header opens the same execution on the Deployment History screen.

Deployment History (execution log)#

Deployment History (eyebrow Execution log) lists finished executions with status Completed, Failed, Cancelled, or Partial Success, most recently completed first. Use the status drop-down to show only one of those states (All Statuses shows all four). The table is paged; the page size follows the default page size in General Settings.

Unlike the Active board, the history view is a snapshot taken when the page loads. Use the refresh button to reload it.

Execution record: per-machine, per-step results#

Opening an execution shows:

• Summary — package, Started At, Completed At, Duration, and Succeeded / Failed / Total machine counts.
• Agent Results — a split view. On the left, every targeted machine with its Progress (steps completed or skipped out of the package’s total) and status. Search by hostname with Search agents…, narrow the list with the status filter (Completed, Failed, Running, Pending), and reset both with the refresh button. The list is paged with the same page size as the main table.
• Step output — on the right. Selecting a machine expands its steps and opens step 1 automatically; click any other step to switch. You see the step status, its exit code, how long it took, and the captured Output and Error streams. A skipped step shows Skipped: and the reason. A step that never ran on that machine shows Step not executed, or the machine’s error message if it reported one — for example the timeout message written when a machine never reported back (see Deployment Timeouts).

Deleting history#

Athena does not age out deployment history automatically. Finished executions stay until you delete them. Users with deployments.manage have two options on the Deployment History screen:

• Delete (per row) — permanently removes one execution and all of its machine and step results.
• Delete All (page header) — permanently removes every finished execution and its results.

Both ask for confirmation and cannot be undone. In addition:

• Executions that are still Pending, Scheduled, or Running are never deleted. A single delete is refused, and Delete All skips them.
• Each delete is written to the audit log as a Deployment event, with the user who performed it. Delete All is recorded with the number of executions it removed.
• Deleting a deployment package also deletes the execution history of that package.

REST API#

The full result of any execution, active or finished, is available over the JWT-authenticated REST API on port 8443. It requires the packages.view permission.

The execution ID is returned when you start a deployment (POST api/deployment-packages/{id}/deploy, or Start-AthenaDeploymentPackageDeployment in PowerShell). It is also the last part of the address when you have the execution open in the console.

# Fetch one execution with all machine and step results
curl -k -H "Authorization: Bearer <token>" \
  https://athena.example.com:8443/api/deployment-packages/executions/<executionId>

Useful fields in the returned execution include:

Troubleshooting#

Related#

• Software Deployment — build, target, and schedule deployments.
• Deployment Package Steps — step conditions, success exit codes, and continue-on-error.
• Deployment Timeouts — how stuck executions are finalized and how the overall status is decided.
• Permission Model & Role Bundles — granting deployments.view / manage / execute.
• Audit Event Types Reference — deployment events in the audit log.