Telegram + GPT bot

Why this breaks in production

• high

  Nobody gets alerted when this workflow fails

  You may think an email or invoice finished when it actually stopped halfway - and no one is paged.

  Fix → In n8n Settings, set an Error Workflow (or add an Error Trigger flow) that Slack/emails your team with the failed run link.

• high

  "Telegram" can fail with no backup path

  Customers get silence, duplicate retries, or a half-finished experience with no internal alert.

  Fix → Turn on retry for transient SMTP/API errors, and route hard failures to an error branch that alerts someone.

• high

  Ran twice when the same event arrived again

  1 outbound action(s) ran again on the second delivery. In production that means duplicate emails, charges, or messages for the same event.

  Fix → Before you send email or charge a card, store the order/message id. If that id was already handled, skip. Put a short queue in front of bursts so one webhook storm cannot spam.

• high

  Kept firing outbound actions across a 10× burst

  9 of those actions happened after the first run. Example from the ledger: 50 near-identical chat messages posted.

  Fix → Before you send email or charge a card, store the order/message id. If that id was already handled, skip. Put a short queue in front of bursts so one webhook storm cannot spam.