Activity & Events

Use the Activity Center to follow background operations, such as image pulls and deploys, and read their output from anywhere. Use the Event Log as the long-term audit trail for an environment.

Follow an activity

Open the Activity Center from the sidebar or mobile navigation bar and select an activity.

Note

Activity output, like build output, shows the docker command’s text and colors, as in a terminal.

Find an operation in the Activity Center and open it to inspect its output.

×

Find an operation in the Activity Center and open it to inspect its output.

Arcane tracks image pulls, builds, and update checks; project pull, build, deploy, redeploy, down, restart, and destroy; container start, stop, restart, redeploy, and delete; vulnerability scans and system prunes.

Status	Meaning
Queued	Waiting for a free slot.
Running	In progress.
Completed	Finished successfully.
Failed	Finished with an error; the output says why.
Cancelled	Stopped before it finished.

If an activity is interrupted, for example by an Arcane restart, a background check marks it Failed so it doesn’t stay stuck in Running. For projects, you can also attach to a running operation with Watch output; see Projects.

Set retention and concurrency

These settings are per environment. Open Settings → Activity and pick the environment under Applying settings for:

• Retention Days: how long finished activities are kept.
• Maximum Entries: a hard cap on stored activity history.
• Concurrent Activity Limit: how many activities run at once. Extra ones wait in Queued.
• Upgrade Log Retention: days to keep self-upgrade log files. Cleanup runs hourly. Default 3; 0 keeps them indefinitely.

Review automation runs

With the jobs:manage permission, open Settings → Automations and open Run history for a job, or open the environment’s History tab under Environments. You see each run’s attempts, errors, per-target results, and operation output when it has an activity. Image update checks, auto updates, vulnerability scans, image patching, GitOps syncs, and backups also list their Steps with status, progress, and failure count.

A queued run on a remote environment shows Waiting for environment until the agent is reachable. Agents on an older Arcane version must be upgraded to report run history. Depending on its state, a run offers Retry run or Cancel pending run; for a failed, partial, or Needs attention run, check its output and the affected resources before you retry.

Review the Event Log

Open Events to view the audit trail. Events outlive the Activity Center’s history.

Use the Event Log to review actions taken in an environment.

×

Use the Event Log to review actions taken in an environment.

Each row shows Severity, Type, User when known, and Timestamp. Search or filter by type and severity, then select a row for details.

The log also records Docker daemon events as they arrive: container exits, out-of-memory kills, unhealthy status changes, and image, network, and volume changes. This includes actions outside Arcane, such as starting a container from the Docker CLI.

Users with audit:read also see audit events: access changes and permission denials. Use Export CSV or Export NDJSON to download the events matching your current filters.