op_provider_unavailable

Last updated Jun 14, 2026

Cause

Several Matter operations depend on external providers — secretary-of-state filing portals, IRS EIN endpoints, banking partners, registered-agent services, e-signature platforms. When the relevant provider is down, in maintenance, or returning gateway errors, Matter surfaces the failure as op_provider_unavailable rather than internalising it. The detail field names which provider is unavailable and (when known) the expected recovery window.

Matter retries provider calls internally with backoff before surfacing this error to the caller. Receiving the error means the platform has exhausted its retry budget for this request and the caller's best move is to retry the whole operation later, idempotently, with the same Idempotency-Key. State at Matter has not been mutated.

Fix

1. Read the detail field for the provider name and any recovery hint.
2. Retry the operation with exponential backoff. Use the same Idempotency-Key so the retry composes safely with the original.
3. Check the public status page at /runbooks/status-page-incidents for an active incident.
4. If the workload is time-sensitive and the provider's outage is extended, surface the delay to the human caller. The platform will not skip the provider.

Related codes

• op_service_degraded — Matter itself is shedding load, not a third-party provider.
• infra_internal_error — the failure originated inside Matter.
• infra_db_unavailable — Matter's primary database is unreachable.

API reference

• Filings — /api-reference/filings
• Banking — /api-reference/banking
• Idempotency — /api/conventions/idempotency