Launch Watchlist
Countdowns, confirmation health and delivery states
Read notification states literally and understand when countdowns become armed.
- Who can use it
- Launch operators and watchers
- Where to find it
- Launch Control → Launch Watch; Community Command → Launch Watch
- Before you start
- A launch with a saved schedule
On this page
Arm countdowns
- Save an exact launch time or launch window in Schedule. A launch window counts down to its start.
- Read the reminder state. Watchlist open can accept opt-ins while countdown delivery remains Not armed yet.
- Advance the launch to Launch approaching through its available next action before the reminder’s due time.
- Check the 24-hour and 1-hour reminder entries. A reminder missed because countdowns were not armed is not promised a retroactive send.
Read confirmation health
| Item | Details |
|---|---|
| Confirmations delivered | Telegram confirmed the tracked private confirmation send. |
| Confirmation failed | The tracked confirmation has a known failure. Read the reason. |
| Outcome unconfirmed | No clear result was returned. It may or may not have arrived and is not automatically resent. |
| Pre-tracking opt-ins | The opt-in predates confirmation diagnostics. Delivery cannot be reconstructed; this is not a failure. |
Different notifications need different actions
Countdowns depend on schedule, lifecycle and member preferences. Manual project updates use Communications. Official contract registration does not send a watcher notice or a community post by itself; those are separate explicit actions in Deploy & Contract. A launch-live alert depends on the eligible live transition and delivery processing.
Troubleshooting
Check schedule, device timezone, lifecycle, opt-in and member countdown preferences before blaming the bot. A queued update is not a delivered update. Avoid repeatedly sending when the outcome is unconfirmed.
Related guides
Set an exact launch time or launch window
Save the schedule and review reminder arming and communication separately.
Understand the launch lifecycle and next action
Follow the available action and its prerequisite instead of skipping stages.
Send a private update to launch watchers
Queue a plain-text project update for eligible active watchers.
Official contract, treasury setup and public launcher limits
Read the verified deployment gates without treating preparation as execution.
A message, reminder or sticker did not arrive
Distinguish audience, queue state, Telegram confirmation and schedule eligibility.