When an investigation or intake cannot proceed, keep the original query and source identities available. Missing evidence, missing access, stale state and uncertain command outcome require different responses.
No starting identity or path
Check the selected dataset, source generation, type, namespace and exact code. Leading zeros and case matter. Another source with the same code is a different identity. A no-match result means not enough information within that question; it does not establish unaffected material or complete physical history.
If the seed exists but the expected path does not, inspect captured relationship types and coverage. A receipt-only source cannot supply a production edge it never recorded. Ask the Supervisor for actual source evidence or a reviewed same-identity bridge. Do not add a guessed relationship from matching dates or quantities.
Stale or expired file review
If the dataset changed after review, use Refresh this review, inspect differences and confirm again. If the private review expired, upload the approved file again. A fresh final preparation is bound to current exact bytes, actor, session and source state.
Scanner unavailable means no file can be reviewed. Retain the source safely and involve support. Do not convert it into another format or disable inspection to create an apparent pass.
Conflicting event content needs source-owner review. Unknown sequence and pending replacement remain explicit. Repeated identical upload is not a correction for changed same-identity content.
Lost command answer
Use the page's reconciliation for the original command. A timeout may follow a committed import, run or decision. Inspect the recorded receipt before repeating. A definite not-applied answer allows a current review of the next action; a denied or unknown answer does not establish failure.
Do not ask another actor to impersonate your request. Current dataset disclosure applies even to retained receipts. Keep the exact action identity when escalating.
Current access was removed
Ask the Supervisor to review legitimate dataset grants and the Owner to review product access. A historic run or case can become unavailable after a required grant is withdrawn. Do not use an unrestricted export or another person's sign-in to bypass that decision.
Report exact dataset, run or review identity, time, visible refusal and intended question through the approved support process. Use Accounts access problems for identity and coverage for interpretation.
Read the technical checks
An Owner or Supervisor can open Health and inspect the current result, detail and work needing a person. Retain the build and displayed failing check when escalating a technical problem. A working browser or healthy service does not verify source history, complete traceability or the physical situation. Resolve the source disclosure or coverage problem through its own guide even when technical checks pass.