Inconclusive evidence

Before resolving an inconclusive result

Use this page when a retest, issue change state or monitoring summary cannot prove that a finding changed. Inconclusive evidence is a limitation state, not a failure to hide. Do not convert an inconclusive result into passed, failed, new or resolved until the missing artifact, changed scope or unavailable evidence reason has been handled.

Review inconclusive evidence

Follow the path `Retest outcome or issue change state → Inconclusive reason → Artifact check → Retry, scope change, or stop`.

1. Open /fix-tasks/{fixTask} or /projects/{project}/monitoring when a retest or comparison is marked inconclusive. Result: missing_artifact_reason and evidence_availability_status are visible before anyone claims a state changed.
2. Read the reason before retrying. Result: unavailable screenshot, missing HTML, skipped page, failed scan or changed scope each has a different next action.
3. Check screenshot, HTML, console and network artifact availability for the affected URL. Result: missing proof is tied to a specific artifact instead of hidden in a generic warning.
4. Confirm whether the scan scope still matches the original issue. Result: scope mismatch remains inconclusive until accepted scope is corrected or a new comparable scan runs.
5. Retry only when the product shows retry is available and safe. Result: transient worker or artifact failures can be retried without bypassing scope, plan or privacy boundaries.
6. Stop or continue by reason. Result: unresolved evidence goes to Retest outcomes, skipped-page guidance, privacy redaction or Monthly summaries with the limitation preserved.

Inconclusive reason meanings

Use the reason label to decide whether the state can be retried, needs scope correction or must remain limited.

• Unavailable screenshot means visual proof is missing and the result cannot claim that the page looked fixed.
• Missing HTML snapshot means DOM-level proof is unavailable for selectors, structure or rendered copy.
• Skipped page means accepted scan coverage did not include the affected URL in this run.
• Scan failed means the worker or browser run did not complete enough checks for comparison.
• Changed scope means the current run did not match the earlier accepted scope or issue context.
• Artifact retention expired means older evidence is no longer available and the limitation must stay visible.

Retry or stop states

Do not retry automatically unless the product says the retry is safe.

• Retry available means the same accepted scope can be scanned again without changing plan, privacy or authorization boundaries.
• Retry blocked means plan, billing, scope or worker state prevents another run.
• Scope correction needed means the customer must return to accepted scope before comparison is useful.
• Privacy redaction needed means evidence exists but cannot be shared until sensitive content is removed or excluded.
• Repeated missing artifact means keep the retest or monitoring result inconclusive and preserve the limitation in summaries.

Continue with limitations

If the limitation belongs to a retest, continue to Retest outcomes with the inconclusive state preserved. If it belongs to monitoring, continue to Issue change states or Monthly summaries without claiming resolution. Use Screenshots and HTML snapshots for artifact-specific proof, Failure and skipped-page meanings for scan coverage gaps, and Privacy redaction when evidence is withheld because it contains sensitive data.