🕒 Scheduler Guide

Why a scheduled Discord message fired at the wrong time — or did not fire at all

Scheduling bugs are often configuration problems rather than bot outages. Time zone assumptions, deleted channels and missing send permissions are the most useful places to check first.

Know which time zone the scheduler uses

Bozos Forever's Scheduler uses IST for its scheduling workflow. If you enter a time while mentally converting from another time zone, the message can be valid but appear at the wrong local hour. Convert the intended time before saving the schedule and verify the displayed schedule afterward.

Confirm the target channel still exists

A scheduled message needs a Discord channel ID. Renaming the target channel does not change its ID, but deleting and recreating the channel does. If the destination was rebuilt, edit the schedule so it points to the new channel.

Check Send Messages permission

The bot must be able to view the target and send messages there when the scheduled time arrives. Channel-level permission overrides can deny access even when the bot has broad server permissions.

Review the saved schedule

Use the scheduler list/view functionality to confirm the target channel, date, time and message are what you intended. This catches simple mistakes before waiting hours for a test.

Use short tests while configuring

When setting up the system for the first time, schedule a harmless test a few minutes ahead in a private channel. Once that succeeds, create the real announcement. Testing a month-long schedule immediately is slower and makes diagnosis harder.

Avoid last-second edits

If you edit or replace a scheduled item very close to its dispatch time, confirm the new record is visible afterward. Give yourself a small buffer when testing so you know whether you are observing the old or updated schedule.

Troubleshooting order

  1. Confirm the schedule exists.
  2. Confirm the IST date and time.
  3. Confirm the target channel ID is current.
  4. Confirm Bozos can view and send in that channel.
  5. Create a short test schedule.
Scheduler documentation →Discord IDs explained →