Understand scheduling on battery, locked screens, and offline computers

Understand page timing on battery, locked screens, sleep, and unavailable networks.

Last checked 21 August 2026

The saved check frequency is a target interval, not an exact appointment. A page can run later when the computer is on battery, locked, asleep, offline, busy, paused, or unable to use its license.

Match the symptom to an action

Checks run about half as often on battery or while locked

While the computer is on battery power or its screen is locked, automatic page checks can take about twice the configured interval:

  • Every 15 minutes can take about 30 minutes.
  • Hourly can take about 2 hours.
  • Daily can take about 2 days.
  • Weekly can take about 2 weeks.

The frequency shown in Monitored Pages does not change. Connect the computer to power and unlock the screen. If the normal interval has already passed, TechDash can pick up the page without waiting for the longer battery or lock period.

Select Run now if the page must be checked immediately. The request still needs a usable license, an internet connection, and available check capacity.

Nothing ran while the computer slept or TechDash was quit

TechDash cannot check pages while the computer is asleep or the app is fully quit. Wake the computer and reopen TechDash. Due work is reconsidered automatically.

Closing the main window is different from quitting. TechDash remains in the tray and can continue checking pages while the computer is awake. To resume monitoring after restarts, turn on Settings > Open at login.

TechDash reports offline or Wi-Fi sign-in required

Automatic checks wait while the computer has no usable internet connection. Join a working network. If the network uses a captive portal, open a browser and complete its Wi-Fi sign-in page.

The saved frequency and Last check do not move forward while no check runs. TechDash retries due work after connectivity returns, although the status may take about a minute to update.

The page is enabled but still does not run

Check these controls:

  • In Monitored Pages, confirm Enabled is On for the page.
  • On the website, confirm monitoring is not Paused.
  • In the tray, confirm Pause all monitoring is not selected.
  • Open Settings > License and confirm the license is active and usable.

After correcting the setting, leave TechDash running and the computer awake. Use Run now when you need an immediate check.

Run now says queued, but the check has not finished

Check queued. means the request is waiting or active, not that it has completed. A large batch, slow websites, or many frequent checks can create a backlog.

Open Queue Status and:

  • Look for the page among waiting or active work.
  • Check whether one website accounts for much of the queue.
  • Allow active checks to finish.
  • Reduce unnecessarily frequent page schedules if backlogs recur.
  • Adjust Settings > Concurrent Crawls only if this computer can handle more or less simultaneous work.

Expected result

After the blocking condition is corrected, TechDash resumes automatic checks without changing the saved page frequency. Overdue work may wait behind other queued checks.

Verify scheduling has resumed

  1. In Monitored Pages, note the page's Last check time.
  2. Select Run now.
  3. Confirm Check queued. appears.
  4. Open Queue Status if the page does not finish promptly.
  5. Return to Monitored Pages and confirm Last check advances after completion.

If the request cannot be queued, follow the message shown by TechDash. If it queues but repeatedly does not complete, use Troubleshoot checks that have stopped running.

If the troubleshooting steps do not identify a pause, connectivity, license, power, or backlog cause, open Help & Support. Include the TechDash version, operating system, hostname and path, saved interval, last-check text, power and lock state, tray connectivity text, manual request time with time zone, and screenshots of the page row and Queue Status.

Related articles