{"version":"2.1.246","anchor":"queued-task-notifications-record-why-they-were-drained","canonical_anchor":"queued-task-notifications-record-why-they-were-drained","heading":"Queued task notifications record why they were drained","tier":"internal","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/queued-task-notifications-record-why-they-were-drained","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Queued task notifications record why they were drained\n\nQueued task notifications now record whether they were delivered or dropped because the agent stopped.\n\n**What**\n\nBoth the interactive and the headless routers that deliver task notifications now attach a reason when clearing queued events: `delivered_to_agent` once delivery is committed, and `agent_stopped` when the target agent has stopped and the events are discarded. Previously the calls passed only the list.\n\n**Evidence**\n\n`delivered_to_agent`\n\n- Area: Background Tasks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}