{"version":"2.1.247","anchor":"orphaned-background-tasks-are-deduplicated-before-you-are-to","canonical_anchor":"orphaned-background-tasks-are-deduplicated-before-you-are-to","heading":"Orphaned background tasks are deduplicated before you are told about them","tier":"internal","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/orphaned-background-tasks-are-deduplicated-before-you-are-to","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Orphaned background tasks are deduplicated before you are told about them\n\nOrphaned background tasks after a cloud restart are deduplicated before you get the notice.\n\n**What**\n\nAfter a cloud worker restart, the lists of running tasks and tasks awaiting notification are merged through one shared deduplication helper instead of hand-written map merging, and if a task was still running an extra wait happens before the orphaned-task notice is shown. The component that restores MCP tasks is now also given the app-state setter, so restored tasks can write back into app state.\n\n**Details**\n\n- On the `CLAUDE_CODE_RESUME_INTERRUPTED_TURN` path.\n\n**Evidence**\n\n`orphaned_background_tasks_pending_notification`\n\n- Area: Background Tasks\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}