[Bug Bash 4/20] Failed mission creates runaway threads and inflates Missions count

[joe-rlo]

Environment

hosted-staging (crab shack)

Version / Commit Hash

v0.25.0 (staging)

QA Test Date

2026-04-20

Feature Area

Missions → error handling

Steps to Reproduce

1. Create a routine/mission that fetches a GitHub API endpoint
2. 2. Let the fetch fail (e.g., use an invalid endpoint or let auth expire)
3. 3. Wait for multiple mission cycles to execute
4. 4. Navigate to the Missions page and observe thread count

Expected Behavior

A failed fetch should be recorded as a status update within the existing mission thread. The Missions count should remain stable and not create new threads for each failure.

Actual Behavior

Each failed mission cycle creates a new thread instead of updating the existing one. The Missions count keeps inflating (observed going from 15 to 29+ threads). This creates runaway thread creation that does not stop until the mission is manually deleted.

Logs / Screenshots

Missions count observed: 15 threads initially, grew to 29+ within minutes. Each failed cycle spawns a new thread. Related to existing issue #2585 (missions count incorrect).

Pre-submit checklist

• Title is specific (not "fix Google Suite" but "Google Suite install throws invalid_grant on OAuth step")
• Commit hash is filled in
• Steps are numbered and reproducible