Understand Queue Status
See scheduled workload, workers, backlogs, hotspots, and website pressure.
Last checked 20 August 2026
Queue Status is the operational view of the work TechDash runs on your computer. It helps you distinguish normal queued activity from sustained pressure that can delay monitoring.
The page refreshes its report every 10 seconds while it is open. Values are snapshots, so they can rise or fall between refreshes.
Queues
The Queues table lists these scheduler lanes:
- Page checks
- Site resources
- SSL
- Domain
- DNS
- Search Console weekly
- Search Console URL inspection
- Screenshots
- Icons
Each lane reports Waiting Jobs, Active Jobs, and Workers. Waiting jobs have been admitted to that in-memory queue but have not started. Active jobs are currently in flight. Workers are the queue's concurrency allowance, not a count of operating-system processes.
A Hotspot badge appears when waiting jobs reach at least the greater of eight jobs or three times that lane's worker count. For example, the threshold is eight with one or two workers, 12 with four workers, and 18 with six workers.
Page checks use the Concurrent Crawls value in Settings > Monitoring, within the computer's hardware cap. Other lanes have their own concurrency and rate controls because they perform different kinds of work or use external services.
Hotspots
The Hotspots card combines queue backlogs with website and page-level load signals. It can show:
- a queue backlog
- a page whose latest check took at least 15 seconds
- a page with at least 250,000 bytes of stored gzipped HTML
- a site estimated at 200 or more checks per day
- a site with at least 40 enabled monitored pages
For slow pages and large HTML, TechDash shows at most the five largest examples of each type. A hotspot is an operational clue. It does not create an incident or prove an SEO problem.
Website Pressure
The Website Pressure table ranks sites by a calculated load score. It uses enabled pages, queued page checks, pages with slow latest checks, pages with large stored HTML, and estimated checks per day. Higher scores appear first, with website name as the tie-breaker.
The table also displays Schedule, Avg check, total stored gzipped HTML, and Pressure. A paused site remains visible if it has enabled pages, and receives a Paused badge.
Pressure is about local monitoring demand, not site quality. A technically healthy site can rank first because it has many frequently checked pages.
Read colors in context
Green, amber, and red indicate good, watch, and concerning operational values. Thresholds differ by column. For example, eight queued pages are red, while 40 enabled pages are red and an average check reaches red at 15 seconds.
These colors are separate from Advisory, Warning, and Critical incident severity. They do not affect Health Score.
When to use Queue Status
Open this page when:
- page last-check times are becoming stale
- a screenshot or icon refresh is delayed
- checks seem to arrive in bursts after startup or resume
- the computer feels busy while TechDash runs
- you want to decide which site's frequency or page count to reduce
A short spike is often normal after launch, wake, reconnecting, or adding many pages. Watch two or more refreshes. If waiting falls, the queue is draining. If waiting grows while workers stay occupied, workload is arriving faster than it can be processed. If waiting grows while Active Jobs remains zero, check license state, monitoring pause, connectivity, and application errors.