Quick user guide

DisDoveOnTime 0.3.18

Schedule Discord webhook posts from your own Windows PC. Add a webhook target, write a post, preview what will be sent, then let the app send it at the selected local time.

Start setup
PlatformWindows x64
Version0.3.18
Works withDiscord webhooks
ImportantThe app must be running to send posts.

5 Minute Setup

Install

Download DisDoveOnTime-0.3.18-win64.zip, extract it to a normal folder, then run DisDoveOnTime.exe.

Create a webhook

In Discord, open the target channel settings, go to Integrations, create a webhook, then copy its webhook URL.

Add a target

Open Targets, create a new target, paste the webhook URL, add clear labels, then save it.

Create a post

Open New post, choose a target, write the message, set date and time, add media if needed, then refresh the preview.

Schedule

Check the dry-run preview, schedule the post, and keep the app running until it is sent.

First Post Tutorial

Use this order the first time you set up DisDoveOnTime. After the first successful post, the normal workflow is usually just: choose target, write post, preview, schedule.

  1. Prepare the Discord channel. Open Discord, choose the server and channel, then create a webhook from channel settings. Copy the webhook URL and keep it private.
  2. Open DisDoveOnTime and check Dashboard. The Dashboard should show the app is ready. If warnings are shown, read them before scheduling anything important.
  3. Create your first Target. Go to Targets, click New target, paste the webhook URL, add a clear local name, then Save target.
  4. Test or validate the Target. If the target health warning looks wrong, fix the webhook URL before creating posts.
  5. Create a New post. Choose the saved target, write the message body, optionally add an embed title, then choose the send date and time.
  6. Choose safety options. Keep mention toggles off unless you intentionally want user, role, or @everyone pings. Add media only when the file is within the app limit.
  7. Refresh Dry-run preview. Check the generated preview. This does not send anything to Discord; it helps catch message, mention, and media problems early.
  8. Schedule and monitor. Click Schedule post, then check Posts and Dashboard. Keep the app and computer running until the scheduled time.
  9. After the scheduled time, confirm the result. If the post is Sent, you are done. If it is Backoff or NeedsReview, open Review and inspect the evidence before retrying.

Main Screens

Dashboard

Your quick overview: saved targets, pending posts, queue activity, review items, warnings, and the next scheduled post.

Targets

Manage Discord webhook destinations. Use clear names so you do not accidentally schedule to the wrong channel.

New post

Write content, choose message or embed mode, control mentions, add optional media, preview the payload, then schedule.

Posts

Inspect scheduled, sent, missed, failed, and review-needed posts. Edit, delete, send now, or requeue when appropriate.

Review

Resolve uncertain send results. Inspect evidence before retrying or dismissing an item.

Settings and Log

Adjust safety defaults, retention, restore, support export, and review local diagnostics with secrets expected to stay redacted.

Statuses To Know

Most problems are easier to understand from the status labels. If something is not sent immediately, check Dashboard, Review, and Log before changing the post.

Pending - waiting for scheduled time Queued - being prepared or processed Backoff - Discord asked the app to wait Sent - Discord accepted the send NeedsReview - user decision required Failed or Missed - not sent automatically

Good Habits

  • Use one clear target per Discord destination.
  • Keep webhook URLs private. Treat them like passwords.
  • Use the dry-run preview before scheduling important posts.
  • Keep mentions disabled unless you intentionally want pings.
  • Keep media under the app's 10 MiB guard.
  • Review uncertain sends instead of blindly retrying.

Important: DisDoveOnTime is a local scheduler. If the PC is off, sleeping, offline, or the app is closed, scheduled sending can be delayed or missed depending on your settings.

Quick Troubleshooting

What you see What to check
The post did not send. Make sure the app was running, check Dashboard, then open Review and Log for details.
The app says Discord is waiting or rate-limited. Do not spam retry. Wait for the backoff state to clear, then check the queue again.
A post is in NeedsReview. Open Review, inspect the evidence, then decide whether to retry, dismiss, or edit the post first.
The webhook target looks wrong. Open Targets, validate the URL, confirm server/channel labels, and review impact before editing or deleting it.
You need help debugging. Use the support bundle export. It is designed to be redacted by default, but still review files before sharing.

Backup, Restore, And Cleanup

Backup

Back up your local app data before major updates or before changing many scheduled posts.

Restore

Use restore summaries carefully. Check duplicate IDs and broken target references before accepting a restore.

Retention

Use retention cleanup only after checking what would be deleted and what is protected.

Download Verification

After downloading the release ZIP, you can verify it with SHA256:

f28faa49decc9cbf95683c4344bc81a11720640ae163beae7740314c9899cf7f

PowerShell:

(Get-FileHash .\DisDoveOnTime-0.3.18-win64.zip -Algorithm SHA256).Hash.ToLowerInvariant()