{"version":"2.1.225","anchor":"replies-are-suppressed-when-another-session-already-answered","canonical_anchor":"replies-are-suppressed-when-another-session-already-answered","heading":"Replies are suppressed when another session already answered the summon","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/replies-are-suppressed-when-another-session-already-answered","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Replies are suppressed when another session already answered the summon\n\nIf another session already answered a comment, the duplicate reply is dropped instead of posted.\n\n**What**\n\nIf a summon was already answered in another session, the drafted reply is discarded rather than posted, and the caller is told why.\n\n**Details**\n\n- New `summon_answered` result path reports the reply was not posted and that the standing answer is already in the thread\n- The auto-react flow gained `answeredElsewhereNoticeText` variants for cases where the artifact is published but the reply is withheld\n- Telemetry records `summon_answered_elsewhere`\n\n**Evidence**\n\n`Reply not posted: this summon was already answered in another session, and the standing answer is in the thread.`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}