{"version":"2.1.229","anchor":"artifact-comment-auto-replies-report-why-they-did-not-reply","canonical_anchor":"artifact-comment-auto-replies-report-why-they-did-not-reply","heading":"Artifact comment auto-replies report why they did not reply","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/artifact-comment-auto-replies-report-why-they-did-not-reply","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Artifact comment auto-replies report why they did not reply\n\nAutomatic replies to artifact comments now record why they skipped a thread.\n\n**What**\n\nThe pipeline that reacts to comments on published artifacts now records a status for each comment thread rather than just succeeding or vanishing: declined with a reason such as blocked, auto_reply_off, plan_mode, hourly_cap, loop_guard or denied_by_rule, or failed with compose_failed or post_failed. Threads seen for the first time can be deferred instead of dropped. Nothing in the build resolves whether the surrounding auto-reply feature is on for a given account.\n\n**Evidence**\n\n`\"deferred_first_sight\"`\n\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}