Skip to main content

Discord — Delivery Log

The Delivery log is the history of real Discord delivery attempts. It is the first place to look when a manager says that an announcement did not arrive.

EventSale Discord delivery log

Find a delivery​

Use Search deliveries to look for a template name, part of the message, footer text, or an error. Narrow the result with Status and Channel purpose.

The useful statuses are:

  • Delivered — Discord accepted the message.
  • Queued — EventSale is waiting to process it.
  • Processing — a worker is currently attempting delivery.
  • Failed — the attempt could not be completed.
  • Partial failure — a multi-recipient operation had both successes and failures.
  • Cancelled — the delivery was stopped before completion.

Open a record to inspect the rendered message and the error details. Compare the recorded purpose with the route in Connection. A missing channel, disabled runtime, disabled template, or revoked Discord permission usually explains a failed entry.

Troubleshooting order​

  1. Confirm the Discord server is still connected.
  2. Confirm the target channel still exists and the route is enabled.
  3. Confirm the selected template is enabled.
  4. Confirm the bot still has permission to send and embed messages.
  5. Send a small template test before re-enabling a large campaign.

The log is evidence of delivery attempts; it is not a place to rewrite a campaign. Make the correction in Connection, Templates, or Campaigns and then create a new controlled test.