{"version":"2.1.235","anchor":"background-respawn-telemetry-records-whether-a-comment-monit","canonical_anchor":"background-respawn-telemetry-records-whether-a-comment-monit","heading":"Background-respawn telemetry records whether a comment monitor was carried","tier":"internal","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/background-respawn-telemetry-records-whether-a-comment-monit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### Background-respawn telemetry records whether a comment monitor was carried\n\nBackground-task respawn telemetry now records whether a comment monitor was carried along\n\nThe update path that respawns background work now reports an extra `carried_comment_monitor` field, and the check that can refuse an update is now told whether auto-reply comment monitoring is being carried over. This lets update-blocked-by-background-task data be broken out by whether a comment monitor task was involved.\n\n- Area: Background Tasks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}