Infinite retry loop across Stripe, Make, and Airtable boundary

Questions
, ,
1

:bullseye: What is your goal?

I am auditing a vendor’s architecture and need to decouple a specific webhook latency trap using the Webhook Response module to enforce idempotency before I force them to tear it down.

:thinking: What is the problem & what have you tried?

Vendor built: [Stripe Webhook] → [Airtable Search] → [Gemini API] → [Airtable Update]. Manual testing is flawless. In production, Stripe logs show webhook delivery failures despite Make.com showing successful runs. It is triggering an infinite retry loop and duplicating the Gemini text generation in Airtable. Looking for the exact variable syntax to enforce idempotency.

:clipboard: Error messages or input/output bundles

Stripe Console Log: Webhook delivery failed: connection timed out.
Make.com History Log: Status: Success (Scenario executed fully without native errors).

2

Hey Eldred,

and you are 100% sure this is happening on the same webhook? I suggest contacting Make and Stripe support about this to see why their server is not receiving the correct response.

In the meantime, you can try logging the received webhooks in a data store and checking it for duplicates when stripe tries to resend the same one.