[Automations] Failed catch-up run shows 'Executed just now' and 'No chat session' without interruption details

[ecki]

Short summary

Automations show "Executed just now" for a failed catch-up run, but opening the run shows "No chat session" without failure details or execution output.

Affected version or release

1.1.24.0, manually supplied by the user from the Windows executable version details. Observed on 2026-10-02.

Installation context

GitHub Copilot desktop app on Windows, using Local-host automations in autopilot mode with worktree workspaces.

What happened?

A daily automation missed its scheduled time while the app was not running. A later run was recorded with trigger catch_up. The Automations UI displayed "Executed just now", but clicking the run displayed "No chat session".

The run metadata available through the app's automation tool contained:

• Status: failed
• Trigger: catch_up
• Started: 2026-10-02T08:38:16.592Z
• Completed: 2026-10-02T08:38:42.707Z
• Error: Interrupted by app shutdown
• workspaceExists: true
• workspaceWorktreeMissing: false

Despite the recorded failure and existing workspace, the user could not see these details or inspect what the run actually did from the run view. A transcript could not be retrieved during investigation, so it is not established whether a transcript was created or whether the requested script started.

Steps to reproduce

The following sequence describes the observed scenario; it has not been independently reproduced:

1. Enable a scheduled Local-host automation.
2. Leave the app closed across its scheduled time.
3. Open the app and allow it to start a catch-up run.
4. Close the app before that run finishes.
5. Reopen the app and inspect the automation's latest execution.
6. Observe the "Executed just now" label, then click the run and see "No chat session" without the recorded interruption details or execution output.

Expected behavior

• Distinguish successful execution, failed/aborted execution, and catch-up execution in the automation list.
• Make missed schedules and subsequent catch-up runs understandable, without presenting "Executed" as the only visible outcome.
• Always show run start/end times, status, trigger, and failure reason, even if no chat session exists.
• Preserve and expose any available partial transcript, tool activity, stdout/stderr, and exit status for interrupted runs.
• If interruption occurs before a transcript or output exists, state that explicitly while still showing the run's metadata.

Additional context

This report concerns run-history visibility and interruption diagnostics, not a request for Local-host automations to execute while the desktop app is closed.

Related broader automation feedback: #1182.