{"version":"2.1.248","anchor":"auto-reply-composition-is-now-time-bounded-and-retry-aware","canonical_anchor":"auto-reply-composition-is-now-time-bounded-and-retry-aware","heading":"Auto-reply composition is now time-bounded and retry-aware","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/auto-reply-composition-is-now-time-bounded-and-retry-aware","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Auto-reply composition is now time-bounded and retry-aware\n\nAuto-replies to artifact comments share the edit deadline and stop blaming API retries for slowness.\n\n**What**\n\nComposing an automatic reply to an artifact comment now has the same deadline as composing an edit, and both read the same override key `composeDeadlineMsOverride` instead of the edit-only one. Neither now reports a failure when the only reason it ran long was an API retry.\n\n**Details**\n\n- Timeout telemetry gained a `request_delayed` field, and a new `reply_compose_timeout` event covers the reply path.\n- An edit compose that timed out purely because the request was being retried returns nothing rather than a `timed_out` decision, so no failure reply is posted.\n\n**Evidence**\n\n`reply_compose_timeout`, `composeDeadlineMsOverride`, `request_delayed`\n\n- Area: Artifacts\n- Names: `composeDeadlineMsOverride`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}