Pause and resume one website

Stop scheduling work for one website without deleting it.

Last checked 21 August 2026

Pause one website when its scheduled work should stop temporarily but you still need its configuration, assets, and history. Pausing is suitable for maintenance windows, dormant client work, or reducing load without deleting evidence.

Pause monitoring

  1. Open Websites.
  2. Open the website card's context menu.
  3. Select Pause Monitoring.

The card shows a Paused badge. The same badge appears beside the website name on its overview page.

Pausing changes the website's stored monitoring state. Schedulers and workers check that state before starting page checks, site-resource checks, SSL, domain, DNS, Search Console, and weekly brand work. Work that is already running when you pause can finish before the state is observed, so do not use Pause as an emergency way to terminate a network request already in progress.

What you can still do while paused

Pausing does not hide or erase the website. You can still:

  • Open the website overview.
  • Review existing incidents, check results, lookup details, and monitored pages.
  • Edit the website's name, address, frequency, credentials, or user agent.
  • Keep its Search Console connection and custom checks.
  • View its locally stored HTML, screenshot, and icon.

Displayed information can become stale while monitoring is paused because scheduled work no longer refreshes it. A pause does not mark open incidents as resolved.

Resume monitoring

  1. Open Websites.
  2. Open the paused website card's context menu.
  3. Select Unpause Monitoring.

The Paused badge disappears. TechDash immediately asks its schedulers to consider due page checks, site resources, lookups, and brand assets again. This makes due work eligible, but it does not force every check to run at once.

Actual start times still depend on:

  • Whether the computer is online and past any captive Wi-Fi sign-in.
  • Whether the TechDash license is usable.
  • Each page's enabled state and due time.
  • Queue capacity and the configured concurrent crawl limit.
  • Search Console quotas and its own schedule.

Use a page row's Run now action if a particular page needs an immediate check after resuming. Use Check now in Site Resources for an immediate resource run.

Portfolio-wide pause

The tray's Pause all monitoring sets every stored website to paused. It is not a separate master switch that remembers each site's previous state. Consequently, selecting Resume all monitoring later unpauses every website, including a website you had individually paused before the portfolio-wide action.

If some websites must remain paused, use Resume all monitoring, then pause those individual cards again.

Pause or delete?

Choose Pause when you expect to return to the website or need to preserve its records. Choose Delete Website only when the website and its local data should be permanently removed from this installation. There is no restore action for a deleted website.

If the website appears to keep running

  • Confirm the card and website overview show Paused.
  • A job that started before the pause may complete and update the interface once.
  • Make sure you paused the intended card when names are similar.
  • If the badge disappeared, a later Resume all monitoring action may have unpaused it.
  • Existing incident timestamps and check history remain visible; they do not prove a new check ran after the pause.

If the Paused badge or saved state changes unexpectedly after a full restart, or new work repeatedly starts after the pause was already visible, open Help & Support. Include the TechDash version, operating system, hostname, action and time with time zone, badge state before and after restart, affected job type, and a screenshot of Queue Status.

Related articles