🐛 Bug - Processing failed for "SSW EagleEye – Sprint Review, Retro and Planning" transcript, Restart also fails

Cc: @calumjs @joshbermanssw @yaqi-lyu @0xharkirat @TobyChurches @adamcogan
Hi Team!

Pain

Tiger failed to process the transcript for SSW EagleEye – Sprint Review, Retro and Planning today (24 Aug 2026). The Teams "Workflows" card reported Processing Failed at 11:32. I clicked Restart and it failed again at 11:40 with the identical card, so the retry path doesn't recover it.

The card gives no error detail or reason, so as a user I have no way to tell whether the transcript, the job, or the model call is the problem — only that "Processing for this meeting transcript failed."

• Project: General Project
• Meeting: SSW EagleEye – Sprint Review, Retro and Planning
• Status: ❌ Failed (11:32), ❌ Failed again after Restart (11:40)

Possibly related to #151 (job executions failing).

Acceptance Criteria

1. The SSW EagleEye Sprint Review, Retro and Planning transcript (24 Aug 2026) is processed successfully and the summary is generated
2. Root cause of the failure is identified and fixed (or documented if it was transient)
3. The "Processing Failed" card includes a short reason / error hint so users know whether Restart is likely to help

Reproduce Steps

1. Hold the SSW EagleEye – Sprint Review, Retro and Planning meeting with Tiger attached (General Project)
2. Wait for Tiger to process the transcript
3. Observe the "SSW Tiger – Processing Failed" card posted by Workflows in Teams at 11:32
4. Click Restart
5. See error – a second identical "Processing Failed" card is posted at 11:40

Screenshot

Thanks!

Start by reproducing the SSW EagleEye transcript failure and its Restart path in the Teams Workflows card, then trace whether the transcript, job execution, or model call fails. No file or test is named; done means the transcript summary is generated, the root cause is fixed or documented, and the failure card gives a useful reason or retry hint.