Slow scans

Most scans complete in roughly a couple of minutes, but duration varies with site size, crawl depth, analysis load, and probe fan-out. Trigger.dev orchestrates the pipeline, so you may see queued → running → analyzing progress before the report unlocks.

What is normal

• Small marketing sites: often near the ~2 minute experience described in product docs
• Larger sites: longer crawl and analyze phases as page counts grow
• Full mode: core report may appear before probe/discovery finish enriching (parallel work)
• Brief queued time when the worker pool is busy

Why scans slow down

• Slow origin TTFB or rate-limited responses
• Bot challenges adding latency or retries
• Very large sitemaps / many URLs discovered
• Heavy analyze prompts or retries after transient AI errors
• Provider latency during probe
• Timeouts that eventually fail the step (see Scan failed)

If it feels stuck

1. 1

   Wait out one full cycle

   Give the run several minutes. Trigger.dev retries transient failures with backoff.

2. 2

   Check for progress signals

   Watch status, pages crawled, and whether a report row appears. Partial completion is progress.

3. 3

   Verify the site is responsive

   If your origin is degraded, fix hosting first — crawls will stay slow or time out.

4. 4

   Avoid duplicate starts

   Multiple overlapping scans on the same project add queue pressure without helping.

5. 5

   Follow recovery if status never moves

   Use Recovery steps and contact support with the scan ID.

Edge cases

• Monitoring rescans — scheduled full pipelines can take longer than a first small scan.
• Competitor batches — multiple core scans increase wall-clock time even though each omits probe.
• Free lifetime gate — “slow” is not the same as “blocked from starting”; upgrade prompts are entitlement, not latency.

When to contact support

• A scan stays queued/running far beyond normal with no page or report progress
• Repeated timeouts on a site that is fast in public checks
• Progress UI contradicts scan status for an extended period

FAQ