Why Trello webhooks fail, vanish or fire twice
Register one with POST /1/tokens/{token}/webhooks, passing callbackURL and idModel (a board, card, member or Workspace ID).
The webhook won't create
How you'll know: The create call fails even though your endpoint works.
Fix: Trello sends a HEAD request to the callback URL first and needs a 200 back. Many frameworks only route POST. Answer HEAD too, and make sure nothing like a login wall or proxy sits in front of it.
It worked for a month, then disappeared
How you'll know: No more events, and the webhook no longer shows up for the token.
Fix: A webhook belongs to the token that made it. If that token expires (a 30days token, say) or is revoked, the webhook is deleted with it. Use a long-lived service token, and check your registrations on a schedule.
The same change arrives twice
How you'll know: Your handler created two records for one card move.
Fix: When a delivery fails, Trello retries up to three times: after 30, 60 and 120 seconds. A slow handler can get a retry while it's still working. Reply quickly, do the work afterwards, and skip any action ID you've already processed.
Signatures don't match
How you'll know: Your check of the X-Trello-Webhook header rejects real requests.
Fix: It's a base64 HMAC-SHA1 of the raw request body plus the callback URL exactly as you registered it, signed with your app secret. A trailing slash or a re-serialized body breaks it.
Your endpoint was down for days
How you'll know: Events from the outage never arrive.
Fix: Retries stop after the third try, so those events are gone. Re-read the affected boards with the API to catch up. Trello only disables a webhook after 30 days and more than 1,000 failures in a row, and replying 410 Gone deletes it on purpose.