Cloud routine session transcripts fail to load ("Something went wrong loading this session")

Summary

Session transcripts for cloud routine (scheduled/triggered) runs fail to load in the claude.ai/code UI. Both the side-panel run view and the full-page session view show only:

Something went wrong loading this session.

This blocks all visibility into what happened during a routine run, which is the only way to diagnose a run that silently fails to complete its task.

Steps to reproduce

1. Open a routine's page, e.g. https://claude.ai/code/routines/trig_01ADygEe1oEZurr2CFD6ZPw1
2. Click into any run in the "Runs" list (reproduced on both Scheduled and Manual runs)
3. Right-hand panel and full-page view both show "Something went wrong loading this session." instead of the transcript

Affected trigger

trig_01ADygEe1oEZurr2CFD6ZPw1 ("Daily Job Scan")

Example session IDs that fail to load

• cse_01DUpJnpfpu6ZHbiQsokgLm2
• session_01XogouKpdoofRNdLhX2rryK
• session_016z1PSpGDyWt9fNTyA1xhsT
• session_01P99wBNNpbHhCGYB1v33gKp

Reproduced consistently across multiple runs over ~24h (2026-08-11 to 2026-08-12), including a run known to have completed successfully in the past (2026-08-10, report committed + email sent) — so it's not limited to failed runs, and not specific to one browser session (confirmed independently in two different browser sessions/accounts).

Secondary issue (possibly related)

Several runs of this routine show status "Completed" in the run list, but the underlying task never actually finished — no git commit, no report file, no email sent, despite the routine's instructions requiring all three each run. Because the transcript is unreadable (see above), there's no way to inspect what happened inside the session or why "Completed" was reported despite no observable side effects.

Impact

No way to diagnose a failing cloud routine run — the one avenue for root-causing it (the session transcript) is broken.