Managing Existing Tasks
Open Scheduled Tasks for the intended server. Backend authentication and guild authorization apply to reads and mutations.
Inspect
Section titled “Inspect”Check each task’s identifier, prompt, due time, target channel and current state. Refresh before acting on an old browser view. Similar prompts can represent distinct tasks; do not identify them by text alone.
Cancel deliberately
Section titled “Cancel deliberately”Use the supported cancellation control for the correct task. Confirm the returned state. Cancellation is not proof that a message already sent to Discord was removed, and it should not be represented as an undo of a completed action.
After errors
Section titled “After errors”Do not submit repeated create/cancel requests without inspecting the current task list. Record the safe task ID and time for support. If an outcome is uncertain, ask for review rather than forcing a replay.
The dashboard task flow is separate from the homepage demonstration. No local marketing control creates, cancels or persists a real scheduled task. See Delivery Behavior.