Skip to main content

Scheduled messages

Scheduled messages let Wardy publish reminders, announcements, or conversation prompts automatically. Open the group in the admin panel, then go to Settings → Scheduled messages. Automation is shown as one compact feature card. Its main switch stops or restores all scheduled deliveries without changing which individual messages were enabled or paused.

If Telegram converts a regular group into a supergroup, Wardy keeps the supergroup's active settings and scheduled messages. The old group entry disappears after synchronization.

Create a scheduled message​

  1. Select Add message, enter the message text, and, if needed, add up to 3 URL buttons. Each button appears on its own row, like welcome-message buttons. There is no separate visible schedule name. You can add several messages with different send times.
  2. Choose where to send it: General chat or one of the topics already known to TG Warden.
  3. Choose Once, Daily, Weekly, or At intervals. A daily or weekly message can have up to 10 unique local-clock send times whose entered values are at least 15 minutes apart; a weekly message uses the same selected times on every selected weekday. For At intervals, choose Repeat interval: 15 or 30 minutes, or 1, 2, 4, 6, or 12 hours.
  4. Check the group timezone in the group header. If it is missing, Automation shows a warning and an action to configure it; Wardy does not substitute UTC. Choose Send without sound if needed. A new message draft is inactive by default; explicitly turn on Message active when it is ready for delivery. When editing an existing message, the switch keeps its current value.

Text and other parameters save automatically after a short pause. The first time a new form becomes valid, Wardy creates one message; later automatic saves update that same message instead of creating duplicates. There are no Save or Cancel actions. Select Done to close the settings: it waits for any pending save. You can close an empty new form without creating a message. The calculated next send appears after the first successful automatic save.

The Telegram Bot API cannot provide a complete list of all existing forum topics. TG Warden adds new or renamed topics to its catalogue when the bot observes them, so they can then appear in the destination list. If a topic is missing, open Don't see the topic?, select Get binding command, and enter a recognizable label from 1 to 128 characters. Wardy creates a one-time /bind_schedule_topic <token> command valid for 15 minutes. The same owner or admin who requested it must send it inside the required real forum topic. Return to the panel and select Refresh topics. The saved label is yours; it does not replace or automatically read the Telegram topic name.

Only a forum-enabled supergroup can bind a topic. Regular groups use General chat, while channels and channel discussions remain excluded.

Use Test to send a test message to the selected destination. While the group remains eligible and you retain permission to manage it, you can edit, pause, resume, or delete a schedule. Pausing one message stops only its future sends. Turning off the Automation switch stops every delivery but preserves each message's enabled or paused choice for when Automation is turned on again. A completed or expired one-time schedule cannot be resumed with its old time; edit it with a future time or delete it.

Availability and limits​

  • Scheduled messages work only in an active regular group or supergroup.
  • They are not available for channel discussions, channels, or private chats.
  • The group timezone must be configured; it is shown in the group header rather than defaulting to UTC.
  • Wardy must remain a group administrator with permission to send messages.
  • A group can have up to 10 scheduled messages in total, including paused messages.
  • For daily and weekly schedules, the entered local-clock values must be at least 15 minutes apart. This validates the selected clock values, not a delivery rate limit. Interval schedules use the available presets; raw cron expressions are not used.
  • Buttons must use valid web URLs. Callback actions and media messages are not included.
Important

Scheduled times use the group timezone. Interval schedules align to the matching local time boundaries in that timezone. During a spring daylight-saving gap, timezone rules move a nonexistent local time forward to the first valid instant, so the actual elapsed interval on that date can be shorter than 15 minutes; during a fall overlap, Wardy does not send the same occurrence twice. Changing the group timezone recalculates the next run of enabled recurring schedules. A one-time schedule remains fixed to its original absolute moment. If Wardy was unavailable, missed interval occurrences are skipped instead of being sent in a burst after recovery.

Tip

Test both the text and the destination before enabling a recurring message. If the target topic is no longer available, pause the schedule and bind a valid topic.

Related articles

Found a mistake? Email bestchatguard@gmail.com. Include the article URL and what should be fixed.