OperationsGuide

Troubleshooting

Common failures and the first thing to check.

Partner API

401 unauthorized — the key is missing, malformed, expired, revoked or inactive. Replace or rotate it; do not retry unchanged.
403 forbidden — the authenticated key lacks the endpoint's required scope.
404 not_found — the resource is unknown or deliberately undisclosed because this client lacks its Program grant or environment access.
409 conflict — an idempotency key was reused with a different request, or an order can no longer make the requested transition.
422 unprocessable — the payload is structurally valid but the Program, item, clinical requirements or serviceability decision prevents the operation.
429 rate_limited — wait for Retry-After, then retry the same logical request and idempotency key.
Missing results — results are exposed only after release; unreleased versions remain pending or undisclosed.

Orders not arriving — confirm the selected environment, Production adapter state, connection validation and transmission history.
Unmapped orderables — complete and validate Catalog mappings; Solia never guesses a laboratory code.
Unresolved clinical policy — inspect Program requirements and governed questions. Manual review is intentional until authority is configured.
Webhook temporary failure — return 2xx quickly, inspect timeout/5xx/429 behavior and bounded Retry-After; retries are scheduled automatically.
Webhook permanent failure or dead letter — correct the endpoint or authorization, then use supported replay rather than creating a duplicate subscription.
Sandbox/Production confusion — verify the environment label and credential prefix; credentials, Programs, adapters and records never cross the pair.