Skip to content
Fork Docs
Guide v1

Task Delivery Problems

No scheduling confirmation

Section titled “No scheduling confirmation”

Inspect Scheduled Tasks in the intended server’s dashboard before creating another reminder. A conversational promise is not proof of persistence, but a missing confirmation is not proof no task exists either.

Stored task did not appear in the expected channel

Section titled “Stored task did not appear in the expected channel”

Check the stored destination and due time. The AI scheduling path uses the current server channel; mentioning another channel in prose does not guarantee it was selected. Verify Fork can view/send there.

Due task has an uncertain result

Section titled “Due task has an uncertain result”

Check actual channel messages, current task state and service availability. Do not blindly replay. Provider, runtime or Discord failures can affect execution and result recording differently.

Retain only safe task IDs/times for support. See Delivery Behavior and Managing Existing Tasks. This guide does not promise exact-time delivery or a recurring-cron interface.