{"version":"2.1.323","anchor":"background-service-message-for-missing-credentials-on-resu","canonical_anchor":"background-service-message-for-missing-credentials-on-resu","heading":"Clear message when a background session lacks the credentials to send","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/background-service-message-for-missing-credentials-on-resu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Clear message when a background session lacks the credentials to send\n\nA background session missing its API key, token or workload identity now says nothing was sent and how to fix it\n\n**What**\n\nA background session is a Claude Code session that keeps running without a terminal open. If the background service does not have the session's API key, token or workload identity, Claude Code now says \"Nothing was sent: the background service lacks this session's API key, token or workload identity.\" It offers two fixes:\n\n- Add the credential to your settings.\n\n- Run `claude stop <id>`, then `claude --resume` in a shell that has the credential.\n\n**Why**\n\nInstead of a vague failure, you get a clear path to getting the session working again.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}