Skip to main content

Documentation for Tutela v3.9.0.

Inspection unavailable or blocked

Use this runbook when the client reports unavailable inspection or work is blocked unexpectedly. A policy intentionally blocking a request and inspection failing to complete are different conditions.

Prerequisites​

  • The visible message, request ID, affected client and time.
  • An administrator who can inspect the effective policy and outage behavior for that connection.
  • A deployment operator for failed dependencies.

Investigate​

  1. Read the exact client message and inspect the matching Activity record if available. Identify a policy decision, approval requirement, extraction failure or inspection-unavailable result.

  2. Open Settings > Support & diagnostics > Service health. Record whether inspector, classifier, policy or another dependency is unavailable.

  3. Have the administrator confirm outage behavior for this specific connection. Browser/file, portal chat, SDK and tool paths can differ. Do not infer a fail-open or fail-closed setting from another client's behavior.

  4. In Grafana, compare inspection results with failure stages:

    sum(rate(tutela_inspection_result_total[5m])) by (action, action_reason)
    sum(rate(tutela_inspector_failure_total[5m])) by (stage, flow, reason)

    Content that was not read in full has partial coverage, reported separately from an inspection failure. The applicable policy and route settings can still block it; successful extraction of part of a file does not establish permission to send the whole file. Coverage is counted separately, by reason:

    sum(rate(tutela_inspection_coverage_total[5m])) by (flow, status, reason)
  5. For a browser problem after an update, reload the existing AI tab and check the site's coverage state. Connected does not establish interception on that page.

Correct the cause​

ResultAction
Deliberate policy blockReview the matching policy and request scope with its owner. Do not treat the block as an availability incident.
Approval requiredHave an eligible reviewer inspect the proposal; the requester resumes only after approval.
Unavailable serviceRepair the named dependency using Service unavailable.
File cannot be extracted or is only partly readUse a supported synthetic file to isolate format/size issues. Do not describe the original file as fully inspected or redacted.
Site interception unavailableCheck support for the site and reload the tab after updating the extension.

Keep the configured enforcement posture while repairing the cause. Any temporary exception needs the responsible administrator's explicit scope and expiration; record the previous setting and its restoration plan.

Expected outcome and recovery​

A known synthetic request on the affected connection completes inspection and produces the expected policy result and Activity record. For a file issue, confirm the entire supported test file was processed. An HTTP success or merely changing outage behavior is not evidence of restored inspection.

Support handoff​

Escalate when required work remains blocked or traffic proceeds without inspection. Include the affected connection, effective outage setting, failure stage, client version, time and request ID, without prompt/file contents.

Next steps​