{"version":"2.1.318","anchor":"background-task-failure-reasons-reworded-new-connector-chan","canonical_anchor":"background-task-failure-reasons-reworded-new-connector-chan","heading":"Clearer reasons when Claude Code stops tracking a background connector task","tier":"notice","area":"Connectors","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/background-task-failure-reasons-reworded-new-connector-chan","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Clearer reasons when Claude Code stops tracking a background connector task\n\nMessages for dropped remote tasks are reworded, with a new reason for when a different connector now holds the task's name\n\n**What**\n\nSome tools from connected services run as background tasks, and Claude Code checks on them now and then. The messages that explain why Claude Code stopped tracking such a task are reworded.\n\n- A new reason: the connector that now has this name does not match the one that ran the task, so Claude Code did not ask it about the task.\n\n- Failed status checks now say that status requests for this task failed and Claude Code has stopped asking. Before, they said the server refused to report on the task.\n\n**Why**\n\nYou see a more accurate reason when a background task is dropped, so you can tell a renamed or replaced connector apart from one that kept failing.\n\n- Area: Connectors\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}