🐛 Bug - Failed runs are reported as "Processing Stopped", identical to a user cancel

Cc:
Hi Team!

🟥 Watch the video (1 min 18 sec) - yt

Pain

Recorded the SSW TV Sprint Review on 19/08/2026 and never got a "Processing Started" card. Got "Processing Stopped" instead - the exact card you get when you cancel a run. I hadn't cancelled anything.

2 bugs:

1. The run failed. Graph 404 fetching the transcript, 3 attempts (downloadTranscript.js:301). It dies before the "started" card is sent, so there's no sign it even tried. No meeting processed end-to-end on 19/08 at all.
2. The card lied about it. The container correctly sent failed, but the TigerTeams Logic App renders the failed case with the same card as cancelled - "Processing Stopped" / ⏹️ Stopped. Failures are indistinguishable from user cancels.

Acceptance Criteria

1. Logic App failed case gets its own card - e.g. "Processing Failed" / ❌ Failed.
2. Graph 404 on transcript fetch is retried with backoff before the run is declared failed.
3. Function App emits telemetry - both App Insights instances are empty, so the webhook side is a black box.

Screenshot

Thanks!

Start by tracing the Logic App's failed-state rendering and the Function App transcript-fetch path at downloadTranscript.js:301. Inspect retry behavior for the Graph 404 and the empty Application Insights instances. Done means failed runs show a distinct card, transcript fetches retry with backoff, and telemetry is emitted to both App Insights instances.