Skip to content

Troubleshooting

  1. Open System status to check for a wider service problem.
  2. Confirm Weatherly is still installed in the server.
  3. Open Feeds and verify the destination channel still exists.
  4. Check View Channel, Send Messages, and Embed Links in that channel.
  5. Review the latest delivery result. A retry is still in progress; a failure needs its visible error checked.

Use Post now in the dashboard after correcting the issue, then wait for the result.

Confirm you signed in with the right Discord account. You need Manage Server or Administrator to configure a server. Refresh the server list after changing permissions or installing Weatherly.

Check whether you are looking at the roleplay date or the real posting time. They do not have to match.

Review the configured timezone, local posting time, advancement interval, paused state, and next-run timestamp. Read Calendars & roleplay dates before changing the fictional date to fix a scheduling problem.

The current world may not have a saved weather day yet. Check whether setup finished and whether the initial run succeeded. Capture the visible run result if it failed.

Use commands inside the server, not in a direct message. Check the command reference for the current supported behavior.

Use the dashboard’s Post now control when the Discord command reports that posting is unavailable.

Delivery may fail or retry even when the dashboard loads. Check Weatherly’s status page and the linked Discord status page.

Avoid repeatedly changing working permissions during a provider outage. Recheck delivery after service recovers.

Open a private support ticket with the server ID, selected world, approximate time, and visible error or run status.