Readiness returns 503

Check Postgres and Redis connectivity, required migration state, ordinary-worker and scanner heartbeat requirements, enabled provider credentials, and startup invariant logs. The response is intentionally generic; use process logs and safe health projections for the exact failing check.

A monitor has no changes

  1. Confirm the source is active and its latest monitor run succeeded.
  2. Confirm a baseline snapshot exists.
  3. Check whether the canonical content actually changed.
  4. Inspect whether a candidate signal is still judge_queued or became refuted.
  5. Confirm the workspace still has a watch on the entity.
The first capture establishes a baseline and does not create a synthetic change.

Firecrawl or Exa is throttled

Lower the provider’s concurrency and request/result budgets, inspect durable acquisition jobs, and allow bounded retries to reconcile. Disable the affected provider gate if pressure continues. Do not enable broad direct fallback or retry-storm the provider.

MCP introspection fails

Check the HTTPS endpoint, SSRF decision, requested versus advertised capabilities, page/item/byte limits, timeout settings, and referenced authentication payload. Rotate or reseal the reference instead of inserting a token into the locator.

Deliveries duplicate or dead-letter

At-least-once transport can retry after an ambiguous external acceptance. Confirm the receiver deduplicates X-Lucim-Idempotency-Key. For dead letters, inspect the destination response class and repair the endpoint before re-enabling it.

An MCP tool is missing

Compare the tool with LUCIM_STAGE and the independent sandbox, observation, or evidence gates. Lower-stage servers intentionally omit unavailable tools from tools/list.

Sandbox runs do not start

Confirm admission is enabled, the requested version is approved, immutable digests and conformance identities match, the dedicated worker heartbeat is current, and the provider is reachable. Keep admission closed until all checks pass.
If a secret appears in a log, example, artifact, or git history, revoke and rotate it before continuing diagnosis.