1.0.0-rc.1 · Release Candidate2 min read
Failure and Degraded Modes
See how AutoCore represents delayed search, media failure, worker gating, provider failure, and partial readiness.
AutoCore treats dependency failure as a state to surface and recover, not as permission to invent success.
| Failure or delay | Source-backed behavior |
|---|---|
| Meilisearch unavailable | Public search falls back to PostgreSQL with the same response shape and a different source indicator. |
| Index delayed or drifted | Search may lag; an administrative reconciliation/reindex concept rebuilds the derived projection. |
| Media processing failed | The asset retains failed state and an error summary; it is not treated as ready. |
| Worker consumption disabled | A requested side effect may remain pending until its rollout and operational gates are enabled. |
| Payment provider unconfigured/disabled | Checkout rejects the attempt; no payment success is inferred. |
| Webhook verification failed | The event is not allowed to mutate the payment state as verified success. |
| Legal profile incomplete | Commercial/legal readiness remains incomplete; templates or fields do not equal approval. |
| Listing rejected/expired/archived | It is not current public inventory; only source-allowed re-entry paths apply. |
Recovery principle
PostgreSQL state, audit history, and provider evidence remain the reference for decisions. Derived stores, queues, and external adapters can be retried or reconciled. Detailed commands, backup, restore, and incident runbooks belong to later documentation phases.
Related articles
Lifecycle and State ReferenceConsolidated source-verified state summaries for installation, listings, media, search, legal, consent, and payments.Data StoresUnderstand what PostgreSQL, Redis, Meilisearch, and media storage own in the AutoCore architecture.Background ProcessingUnderstand AutoCore queue, Worker, indexing, media, notification, and scheduled-processing boundaries.Security and Configuration BoundariesUnderstand AutoCore authentication, authorization, installation, edition, configuration, and external-service boundaries.