Scheduling
Reminders, scheduled messages, birthdays, and sticky messages.
Start here
Schedule a reminder with a clear destination
PulseOne → Dashboard → select your server → Modules → Scheduling
Use Modules → Message builder to publish any reusable content you need.
Open Modules → Scheduling (the Reminders console). Add a reminder under Reminders.
In Where choose its channel or user destination; in Message choose the content or published template.
In When enter the intended date, time, timezone and recurrence.
Save, verify the next scheduled occurrence and watch a near-term test reminder to confirm delivery.
Practical example
Set a weekly staff reminder at a known local time and check how daylight-saving transitions affect its next run.
Before you begin
- Enable first: messages.
- Discord bot permissions for the operational slice: ViewChannel, SendMessages, EmbedLinks.
- Review staff roles and channel access in your server before using the feature.
Overview of the setup
Before you begin
Publish a message template, then choose a personal or server reminder and its schedule.
Configure
Set a timezone and recurrence, and check how missed runs or daylight-saving changes are handled.
Test and verify
Create a near-term test schedule, verify exactly one delivery, then inspect the next scheduled run.
Features explained
What each feature does and what to check before publishing or installing the result.
Scheduled and repeating messages
One-off and recurring schedules depend on the selected time zone and delivered template version.
Personal and server reminders
Personal and server reminders have different destinations and audience privacy expectations.
If it still does not work
- Reminder not sent? Inspect the next run, intended timezone and permission to post to the destination.
- Avoid creating duplicate reminders while an existing delivery is delayed.
Troubleshooting and safety checks
- Late reminder? Check timezone, next-run value, permissions and delivery status; do not create duplicates during retry.
- If a capability is unavailable in the UI, check the module's current rollout/availability instead of assuming every roadmap item is live.