Two parallel requests create the same order twice
Steps to reproduce
- Send two requests concurrently with the same idempotency key.
- Query the order list.
- Check the accounting record.
- Expected
- The second request returns the same order and creates nothing new.
- Actual
- Two separate orders are created and the customer is charged twice.
- Impact
- The idempotency key is never checked. Direct financial impact.
- Evidence
- har-402.json · db-402.sql