Skip to main content

Session Logs

The session log is the live transcript for every Bosun run. It streams agent messages, tool output, status changes, and now exposes direct controls for stopping work mid-flight.

Cancel running tasks​

While a task is queued or running, the log header shows Cancel run. Selecting it cancels the workflow.

Cancelled runs keep their existing log history, artifacts, and usage records. The log header records the stop event so collaborators can see who halted the task and when.

Error handling and retries​

If the stop request fails (network issues or the API rejects it because the run already ended), the UI surfaces the error inline and keeps the button enabled so you can try again. Because the executor enforces cancellation at the workflow level, partial steps do not resume automatically—rerun the task from the beginning if you need a fresh attempt.

Session history view​

Open Session History from the global navigation to review every run you can access across organizations. The table reads directly from the Sessions API, so pagination, search, and filters are applied on the server before the UI renders the result set. Each row surfaces the derived status, repository, pull request (if any), and the most recent timestamps so you can decide whether to drill into the full log.

Cross-links:

  • Code Environment – outlines the session API payloads and runtime overrides.
  • Task Graphs – cancellation immediately halts the graph, so follow-on steps must be retriggered in a new run.