Delivery Behavior
A task’s saved state and a successful Discord delivery are different facts. Execution depends on the running service, current destination access and the result of external calls.
Before the due time
Section titled “Before the due time”Confirm the target channel still exists and Fork can view/send there. A removed role or changed overwrite can invalidate an otherwise valid task. An operator-side pause or provider failure may affect execution.
At delivery
Section titled “At delivery”Treat the actual delivered message and recorded result as evidence. A stored task is not proof of timely delivery, and a missing UI confirmation is not proof the Discord send never occurred.
If uncertain
Section titled “If uncertain”Check the task ID, scheduled time, state and target channel. Do not blindly replay or create a replacement before determining whether delivery occurred. Ask for a redacted operator review if the result remains unknown.
No guaranteed delivery SLA, recurring schedule engine or exactly-once external send guarantee is claimed by this guide. Use Service Status and Task Delivery Troubleshooting for the next checks.