When our gateway throws intermittent 502/504s, we can either auto-retry 2-3 times (saves about 15% of failed collects but we’ve seen the occasional duplicate when a merchant ignores idempotency keys) or stop after one fail and kick to manual review (slower recovery and more client support touchpoints). For those running high-volume cycles, where do you set the line - and are you tagging attempts with a request fingerprint or leaning on gateway idempotency only?