{"version":"2.1.234","anchor":"failure-to-start-the-background-session-for-artifact-comment","canonical_anchor":"failure-to-start-the-background-session-for-artifact-comment","heading":"Failure to start the background session for artifact comments is now reported","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/failure-to-start-the-background-session-for-artifact-comment","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Failure to start the background session for artifact comments is now reported\n\nIf the artifact comment watcher can't start, you're told automatic replies stopped instead of it failing quietly.\n\n**What**\n\nIf the background session that watches your published artifacts for comments cannot be started, each affected artifact gets an explicit message telling you automatic replies have stopped and to publish again to re-enable them, instead of the replies stopping silently. The failure is counted as `adopt_spawn_failed` on `artifact_live_subscribe`.\n\n**Evidence**\n\n`The background session didn't start, so automatic replies to Artifact comments stopped. Publish the Artifact again to turn them back on.`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}