From 2a00339882e2ae55d3783ba748d6068480edabc1 Mon Sep 17 00:00:00 2001 From: Siavash Sameni Date: Wed, 27 May 2026 09:05:21 +0400 Subject: [PATCH] docs(ops): mark Request Network intent idempotency fix as implemented MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Backend solution (c) shipped in nick/backend@bdbcc32 — endpoint now reuses existing pending Payments instead of colliding on the unique index. Co-Authored-By: Claude Opus 4.7 --- .../Handover - Request Network Intent Duplicate Key Bug.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/08 - Operations/Handover - Request Network Intent Duplicate Key Bug.md b/08 - Operations/Handover - Request Network Intent Duplicate Key Bug.md index 67cc2c3..5bdfe00 100644 --- a/08 - Operations/Handover - Request Network Intent Duplicate Key Bug.md +++ b/08 - Operations/Handover - Request Network Intent Duplicate Key Bug.md @@ -72,7 +72,7 @@ Exact payload that reproduces is captured in the original ticket (`amount: 12`, ## 5. Solutions -Three layered fixes. Apply (a) immediately to unblock; (b) and (c) are the durable fix. +Three layered fixes. **(c) is implemented as of 2026-05-27** in `backend/src/services/payment/requestNetwork/{requestNetworkPayInService,requestNetworkRoutes}.ts`. Apply (a) once to clear the existing stuck doc. (b) is a frontend hygiene improvement worth keeping on the backlog but is no longer required to unblock checkouts. ### a) Hot unblock — clear the stale pending document