Auto-Respond Field Lab Yelp workflow · duplicate control

Retries / idempotency

Are these two webhook deliveries the same lead event?

Paste synthetic envelope fields for the original delivery and its retry. The workbench normalises them, builds a deterministic key, and explains whether a second reply should be suppressed.

Use synthetic IDs only. Do not paste a customer's name, phone number, message, address, or any production secret. This page performs no network submission and stores nothing.

Envelope comparison

Ready to compare
A production key should use immutable provider IDs and the provider's documented event type.

Expected retry decision

Not run

Normalised key material

  1. Compare the two synthetic envelopes to inspect the key.

Persist before replying

Claim the immutable event key in a durable store before sending a reply. A process-local set disappears during a restart and cannot protect multiple workers.

Keep states separate

Record received, claimed, reply accepted, failed, and reconciled. A timeout does not prove the provider rejected the message.

Do not over-dedupe

Lead ID alone is too broad when one lead can create several valid messages. Event ID alone may be too narrow if a provider changes IDs across retries.