What runs on a schedule
Renewal notices, event reminders, and the waitlist, without anybody remembering.
Three jobs run unattended. You do not configure them; they are part of how the product behaves, and the platform console shows whether they have run.
| Job | What it does |
|---|---|
| Renewals | Emails members whose membership ends in 30 days, 7 days, and today. Nothing after expiry β a fourth automated message to somebody who has decided to leave is how a club gets marked as spam. |
| Reminders | Emails everyone booked onto an event starting about a day from now, with their ticket. |
| Waitlist | Fills seats freed since the last sweep and tells the people who got them. It never promotes into an event that has already finished. |
- Every send obeys the same channel preferences and opt-outs an announcement does.
- A job claims its period before running, so a retry, a double-click, or a second server cannot double-send.
- One club failing β a bad Telegram token, a bounced address β never stops the others, and what failed is recorded rather than swallowed.