Jobs and monitoring
The Jobs section of the console shows every agent run for your tenant: past, in-flight, and failed.
Jobs list
Section titled “Jobs list”The jobs list shows one row per job, newest first.
| Column | Description |
|---|---|
| Started | When the job was dispatched |
| Agent | The agent name that drove the job |
| Trigger | The GitLab event that fired the trigger |
| Status | Current job lifecycle status (see below) |
| Duration | Elapsed time from start to finish; blank while the job is running |
| Tools | Total number of tool calls made during the job |
| Outcome | Final result once the job is complete; blank while in progress |
Job statuses
Section titled “Job statuses”| Status | Meaning |
|---|---|
STARTING | Container is being allocated and the agent is starting up |
RUNNING | Agent is actively executing |
FINISHING | Job received a stop signal and is winding down |
DONE | Job completed normally |
CANCELED | Job was stopped by a user action, a timeout, or a policy limit |
ERRORED | Job ended unexpectedly — check the event timeline for details |
Outcomes
Section titled “Outcomes”A job has an outcome once it reaches a terminal status (DONE, CANCELED, or ERRORED). The UI shows the literal value as a badge; non-SUCCESS outcomes render red:
- SUCCESS — the agent exited cleanly.
- FAILURE — the agent exited with an error.
- CANCELED — the job was stopped by a user action or a policy limit (timeout, spend cap, admin stop, etc.).
- TIMEOUT — the job was stopped because it exceeded the configured wallclock limit.
In-progress rows show “in progress” in the Outcome column.
Auto-refresh
Section titled “Auto-refresh”The jobs list refreshes in-flight rows automatically every 5 seconds while any job without a final outcome is visible. If the refresh fails (for example, due to a network interruption), a warning banner appears. Historical rows (jobs with a final outcome) are not re-fetched automatically.
Click any row to open the job detail view.
Job detail
Section titled “Job detail”The job detail view shows the full event timeline for a single job, including live streaming while the job is running.
Summary card
Section titled “Summary card”The top of the detail view shows:
- Status and Outcome badges
- Started and Finished timestamps
- Cost — cumulative LLM spend for the job in USD (e.g.
$0.0124) - Tool calls — total count of MCP tool calls
Event timeline
Section titled “Event timeline”The event timeline lists every recorded event in reverse-chronological order (newest at top). Each entry shows the event type, timestamp, and relevant detail.
| Event type | What it shows |
|---|---|
| Status change | Transition to a new lifecycle status, with an optional detail message |
| Tool call | Tool name, outcome (OK or error), and duration in milliseconds |
| Log | A chunk of stdout or stderr output from the agent |
| Final status | Job outcome, exit code, and an optional summary message |
Log entries longer than 300 characters are truncated with a “more” link to expand them.
While a job is in flight, the timeline is live: new events stream in as they happen and are highlighted briefly in green. A LIVE badge appears next to the timeline heading. When the final_status event arrives, the stream closes automatically and the summary card refreshes.
You can pause and resume the live stream using the Pause / Resume button in the summary card. Pausing stops new events from appearing in the timeline; the stream continues in the background and new events are queued.
Canceling a job
Section titled “Canceling a job”The Cancel job button appears in the summary card while a job is in STARTING or RUNNING status. Clicking it sends a stop signal to the running agent. The job transitions to FINISHING while it winds down, then to CANCELED with outcome FAILURE.
The Cancel button is not shown once the job is in FINISHING, DONE, or CANCELED status.