StromDocs

📣 Broadcasts

Plan and send server announcements without babysitting them. Compose a message or rich embeds, target a channel, and publish it now, at a scheduled time, or on a repeating cadence. Strom handles delivery, retries transient failures, and keeps a history of everything it sent.

At a glance
  • Send plain text or rich embeds (up to 10 embeds per broadcast).
  • Publish immediately, once at a future time, or on a recurring schedule.
  • Preview a broadcast before it goes out, and edit it while it’s still pending.
  • Cancel or delete scheduled broadcasts before they fire.
  • Automatic retries on delivery failure, with a failure DM to server managers.
  • Full history of past broadcasts and their outcome.
  • Manage everything from the dashboard or the /broadcast command group.

Scheduling modes

ModeWhen it sends
NowPublished the moment you confirm.
OnceDelivered a single time at the date/time you set.
RepeatDelivered on a recurring schedule (e.g. daily/weekly) until you cancel it. Recurrence is capped to a safe number of runs.

::: info Times are UTC Recurring schedules are evaluated in UTC. When you set a repeating broadcast, translate your local time to UTC so it fires when you expect. :::

The broadcast lifecycle

  1. Create a broadcast — set its title, target channel, and content (text and/or embeds).
  2. Preview it to see exactly how it will render in Discord.
  3. Schedule it (now, once, or repeat) — or leave it as a draft and edit it later.
  4. Strom publishes it at the right time.
  5. If delivery fails, Strom retries on an escalating schedule and notifies managers if it ultimately can’t send.
  6. The result is recorded in history.

Reliability

  • Retries — a failed delivery is retried on an escalating backoff (roughly 15 → 30 → 60 minutes). A one-off broadcast that exhausts its retries is marked failed; a recurring broadcast keeps its schedule and simply skips the missed run.
  • Failure alerts — if a broadcast can’t be delivered, Strom DMs the server owner and members with Manage Server so it never fails silently.
  • Queued delivery — broadcasts run through Strom’s per-guild job queue, so scheduled sends stay reliable even under load.

Permissions

You need Manage Server to create or manage broadcasts. Strom needs, in the target channel:

  • View Channels
  • Send Messages
  • Embed Links (for embed broadcasts)
Check the target channel

If Strom loses access to the target channel (deleted, or permissions changed) after a broadcast is scheduled, delivery will fail and managers will be notified. Keep the channel and Strom’s access intact until the broadcast has sent.

Troubleshooting

::: details My scheduled broadcast didn’t send Confirm Strom can still see and post in the target channel, and that the broadcast wasn’t cancelled. Check the failure DM sent to server managers for the exact reason, and review the broadcast’s status in history. :::

::: details A recurring broadcast stopped Recurring broadcasts run for a capped number of occurrences and stop when that limit is reached or when you cancel them. Re-create it to continue. :::

::: details The embed looks wrong Preview before publishing. Make sure Strom has Embed Links in the channel — without it, embeds won’t render. :::