Mark an incident as resolved

Close an accepted issue until its observed value changes.

Last checked 20 August 2026

Use Mark Resolved when you have reviewed an incident and want to accept its exact current failing value. It removes that incident from the open list without disabling the check.

Typical reasons include:

  • The change was intentional and requires no website correction.
  • The issue was handled outside TechDash, but the monitored value is expected to remain as shown.
  • The finding is temporarily acceptable, while a different future value should still be reviewed.

Do not use it as proof that a website fix worked. Use Check & Verify for that.

Mark the current value resolved

  1. Open the incident.
  2. Read the check description, URL or grouped rows, and current evidence.
  3. Select Mark Resolved.

TechDash stores a local resolution keyed to:

  • Website
  • Monitored path, or the site-level scope when no page path applies
  • Check
  • Current observed value

For most incidents, the observed value is the current evidence. If no current value exists, TechDash uses the incident message. For saved page-HTML evidence, it records the content digest rather than the local storage reference.

The dialog closes, shows Incident marked resolved., and removes the matching card from Incidents.

What Mark Resolved does not do

Marking resolved does not:

  • Rerun the check
  • Change the current result to Good
  • Edit the live website
  • Disable the check
  • Remove the monitored page
  • Create an ignore rule
  • Guarantee a recovery notification

The latest check can still be failing under Latest results even though its matching incident is absent from the open list.

When the incident can return

The resolution suppresses only the same website, scope, check, and observed value. If a later check produces a different failing value, the stored resolution no longer matches and the incident reappears.

Examples:

  • A title-change incident resolved with title A can return if the title changes to B.
  • A grouped duplicate-title incident can return when its set of duplicated values or URLs changes.
  • An expiry incident can return when its represented evidence, such as the observed expiry value, changes. A severity change alone does not invalidate the resolution.
  • A page HTML incident can return when the stored digest changes.

If the check later passes, there is no open failing incident to display. However, the resolution record is not automatically deleted when that happens. If the same check later fails with the same observed value, the existing resolution can continue to suppress it. A different failing value can still reopen it.

This distinction matters when choosing between acceptance and verification. If you corrected the site and want a later recurrence of the same failure to be visible, select Check & Verify instead of Mark Resolved.

Mark Resolved compared with other actions

  • Check & Verify runs the relevant work and closes the incident only if the current derived failure disappears.
  • Mark Resolved accepts this exact current observed failure.
  • Ignore This suppresses the check at a selected URL, website, or global scope until the rule is removed.
  • Update Monitored URL changes an eligible redirecting monitored path and runs a page check.
  • Remove Page deletes an affected page from the monitored set.

If the card does not disappear

Wait for the success message and for the dialog to close. If the action reports an error, the resolution was not confirmed. If a similar card remains, compare its website, URL, check name, and evidence. It may be another incident with a different scope or observed value.

Mark Resolved is stored in the local TechDash database. It applies to this installation's incident view, not to the website, CMS, or an external account.

Related articles