Collect version, platform, queue, and incident details for support

Gather useful evidence without sending the local crawl database.

Last checked 21 August 2026

A focused report helps separate an app problem from a license, connection, queue, website, or individual-check problem. Collect only the details that apply, remove secrets, and describe one problem per report where possible.

Start with the app and computer

If TechDash opens:

  1. Open Settings > Check for Updates and record Current version.
  2. Open Settings > About and record Platform.
  3. Record the operating-system name and version.
  4. If you know it, include whether the computer uses Apple silicon, Intel, x64, or arm64.

If TechDash does not open, use the version shown in the installer or the operating system's application details if it is easy to find. Do not reinstall or modify the app only to discover the version.

Describe exactly what happened

Include:

  • The complete error message, including punctuation
  • The approximate time and your local time zone
  • What you expected to happen
  • What happened instead
  • The shortest sequence that reproduces the problem
  • Whether it affects one URL, one website, one type of work, or every website
  • Whether it happens every time or only sometimes
  • Anything that changed shortly before it began, such as an app or operating-system update, network change, credential change, backup restore, or unexpected shutdown

For a website problem, include the hostname and affected monitored URL. Remove access tokens, session IDs, personal information, and unnecessary query parameters from URLs before sharing them.

Add evidence for the affected area

For an incident, record its exact name, severity, detected time, affected URL, and the relevant expected, previous, current, or error evidence. Say whether it is open, resolved, reopened, or changed after Check & Verify.

You can use the incident Share menu to prepare content for Email, Microsoft Teams, WhatsApp, Telegram, or Copy Markdown. Review and sanitize the prepared text before sending it. A cropped screenshot can also help, but exclude unrelated websites, account details, browser tabs, and webhook values.

For delayed work, open Queue Status and identify the affected row. Record its waiting jobs, active jobs, and workers. For a page backlog, also include the relevant Website Pressure message. Say whether monitoring was paused, the page was enabled, the computer was online and awake, and Run now queued the page or returned an error.

For startup failures, copy Starting TechDash, TechDash failed to connect to the desktop process., or the complete alternative message. Record whether the tray icon remains and whether fully restarting the computer changed the result.

For a crash, include the time, action in progress, version, platform, and whether Settings > Privacy > Send crash reports was On before the crash. The setting being On does not prove that an upload succeeded.

Keep sensitive data out

Do not send these through ordinary email, messaging, or copied incident text:

  • The TechDash database or its related files
  • The TechDash secret-storage file
  • License keys
  • Basic Authentication usernames or passwords
  • Google access or refresh tokens
  • Slack, Microsoft Teams, or Discord webhook URLs
  • Raw crash dump files
  • Complete stored HTML when a short sanitized excerpt is enough

If more sensitive evidence is required, wait for TechDash support to explain what is needed and how to transfer it appropriately.

Open Help & Support

Select Help & Support at the bottom of the TechDash sidebar. It opens https://techdash.com/support in your default browser. Use search or Contact us from there. TechDash does not prepare or submit a support request automatically.

You are ready when your report identifies the app version and platform, gives reproducible steps and a time, includes only relevant evidence, and contains no credentials or unnecessary private data.

Related articles