Reply integrations distinguish failed and unconfirmed sends
What changed
Reader reply delivery distinguishes REPLY_NOT_DELIVERED from DELIVERY_UNCONFIRMED. REST returns these failures with HTTP 409; MCP reports the delivery failure to the caller. Successful reply results include requestId for receipt correlation. An unconfirmed outcome must be checked in the provider thread before another reply is attempted.
Why it matters
Integrations can tell a confirmed failure from a reply that may already have posted, reducing duplicate replies after timeouts.
- Availability
- Reply integrations distinguish failed and unconfirmed sends: Part of the reader-reply rollout after its required migration and deployment.
- What you need to do
- No action required.