Recheck an incident with Check & Verify

Queue the relevant check to confirm whether a reported issue is fixed.

Last checked 20 August 2026

Use Check & Verify after correcting an incident and when you want TechDash to evaluate it immediately. This action runs the work selected for the incident source. It does not merely hide the card or mark the existing evidence as accepted.

  1. Open the incident.
  2. Review the affected URL or rows and How to fix guidance.
  3. Apply the correction on the website, CMS, Search Console connection, certificate, DNS, or other relevant system.
  4. Wait until the public result is available from this computer.
  5. Select Check & Verify.
  6. Keep the dialog open while the action runs.

What TechDash reruns

The incident source determines the verification:

  • A page incident or page-check error runs that monitored page's full check job.
  • A website-level finding recalculates website-level checks from current saved page state.
  • A Search Analytics incident starts the weekly Google Search Console work.
  • A URL Inspection incident starts inspection for the incident URL when one is available.
  • A DNS resolution incident starts a DNS lookup.
  • Other site-resource incidents run site-resource work.
  • A certificate incident starts an SSL lookup.
  • A domain-registration incident starts an RDAP lookup.

The button does not always perform the same kind of crawl. In particular, a website-level verification does not first refresh every monitored page. If a grouped result depends on page snapshots that have not been updated since your fix, run the relevant page checks or wait for their schedule before verifying the grouped incident.

What happens after verification

TechDash rebuilds the current open incident state after the work finishes:

  • If the relevant failure no longer exists, the dialog closes and shows The check passed. This incident is closed.
  • If the incident still exists, the dialog stays open with refreshed evidence and shows The check still fails.
  • If the page was removed, TechDash reports That page is no longer being monitored.
  • If the computer is offline or behind captive Wi-Fi, the check does not run and TechDash shows the corresponding connectivity message.
  • A source-specific failure, such as unsuccessful site-resource work, is returned as an error.

Verification is synchronous from the dialog's point of view. The button shows a spinner and incident actions remain disabled until the requested work returns. Some underlying operations can still take time because they crawl a page, contact an external service, or wait for a hard network deadline.

Recovery notifications

Closing the current incident and sending a recovery notification are separate outcomes. The incident can close whenever its latest derived state no longer fails. A desktop or webhook recovery is sent only when:

  • The app detects an eligible fail-to-pass or open-to-closed transition.
  • Notifications > Notify when a check recovers is On.
  • The check is eligible to notify.
  • The relevant notification channel is configured and enabled.

Built-in Advisory recoveries do not notify because Advisory built-in checks are not notifiable. A closed incident can therefore disappear without any external message.

If verification still fails

  1. Read the refreshed Current, After, URL rows, or table evidence.
  2. Open the live URL from the incident and confirm the expected public state.
  3. Check for caches, delayed deployment, redirect chains, stale DNS, or a Search Console reporting delay.
  4. For website-level checks, refresh the affected monitored pages before recalculating.
  5. Run Check & Verify again only after the evidence should have changed.

Do not use repeated verification as a tight polling loop. External data may not update immediately.

Choose the right alternative

Use Mark Resolved when the current failing value is intentional or already handled and you want to accept that exact observed value. Use Ignore This when the check should be suppressed for a URL, website, or all websites. Those actions do not prove that the underlying check now passes.

Related articles