{"version":"2.1.280","anchor":"background-job-environment-entries-are-now-individually-logg","canonical_anchor":"background-job-environment-entries-are-now-individually-logg","heading":"Background job environment entries are now individually logged when dropped","tier":"notice","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/background-job-environment-entries-are-now-individually-logg","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Background job environment entries are now individually logged when dropped\n\nClaude Code now logs a separate warning for each background job environment variable it drops\n\n**What**\n\nWhen Claude Code runs a background job, it checks the environment variables being passed to it and drops any that fail validation. A new function now logs a separate warning for each dropped variable, naming the variable and the specific reason it was dropped:\n\n- the variable name is invalid\n\n- the variable's value is not a string\n\n- the variable's value contains a NUL character\n\n**Why**\n\nPreviously a dropped environment variable would not be called out individually. Logging each one by name and reason makes it easier to spot why a background job is missing an environment variable it was supposed to have.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}