Troubleshoot checks that have stopped running

Check app, license, pause, page, connectivity, schedule, and queue state.

Last checked 20 August 2026

Start by identifying exactly what is stale. Page checks, site resources, SSL, domain, DNS, Search Console, screenshots, and icons use separate schedules and queues. A current page result does not prove that Search Console ran, and one delayed favicon does not mean all monitoring stopped.

Check whether TechDash is running

Closing the main window leaves TechDash in the tray and monitoring continues. Choosing Quit TechDash, shutting down the computer, signing out, or ending the process stops schedulers.

Open TechDash from the tray. If you expect it to start automatically, check Settings > Monitoring > Open at login. The setting starts TechDash in the background when you sign in, but it cannot run while the computer is off.

Check license and pause state

If the activation screen is shown, monitoring is locked. Activate a valid license before testing checks. An ended updates-and-support date does not stop monitoring, but an invalid, revoked, unlinked, or differently bound license does.

Then check pause controls:

  1. Open the tray menu. If it offers Resume all monitoring, all websites are currently paused.
  2. Open the affected website and confirm it is not paused.
  3. Open Monitored Pages, edit the page, and confirm Enabled is On.

Pausing a website or disabling a page preserves existing results, so stale timestamps are expected until it is resumed.

Check the schedule

The visible intervals are Every 15 minutes, Hourly, Daily, and Weekly. A page is not queued until its saved interval is due. On battery power or while the screen is locked, TechDash stretches page-check intervals to about twice the configured value without changing the saved setting.

Sleep, shutdown, and a locked screen can therefore create a delay. When the computer resumes, due page checks and site resources are reconsidered. Work still enters queues according to available capacity.

Check connectivity

Look at the tray tooltip:

  • TechDash: Waiting for internet means no usable connection was detected.
  • TechDash: Wi-Fi sign-in required means the network appears to require a captive-portal sign-in.

Complete Wi-Fi sign-in in a browser and confirm normal HTTPS access. VPNs, proxies, DNS filters, firewalls, website bot protection, and authentication changes can affect only some destinations.

Test one page

In Monitored Pages, select Run now for one affected page. A manual run can return an immediate blocker:

  • Activate a TechDash license to run page checks.
  • Wi-Fi sign-in is required before TechDash can check pages.
  • This computer is offline. Page checks will resume when internet is available.

If the run queues successfully, open Queue Status. Find Page checks and review waiting jobs, active jobs, and workers. A growing waiting count with active work indicates a backlog, not a stopped scheduler. Avoid selecting Run now repeatedly, because manual runs can add pressure without fixing the cause.

Check the correct queue

Queue Status has separate rows for Page checks, Site resources, SSL, Domain, DNS, Search Console weekly, Search Console URL inspection, Screenshots, and Icons. Use the row that matches the stale data.

Search Console also depends on a valid connected property, Google authorization, property access, its own cadence, and URL Inspection quota. Site resources and lookups have schedules that differ from each page's interval.

If a queue remains inactive after the app is running, licensed, resumed, online, and due, collect its exact row values, the affected website and URL, the last successful time, and the app version for support.

Related articles