{"data":{"slug":"typesense","failure_modes":[{"pattern":"Strict schema enforcement rejects partial documents","impact":"Agent import batches fail when any document has a missing field. Single bad document can cause entire batch rejection depending on import mode.","frequency":"common","workaround":"Use dirty_values: \"coerce_or_drop\" in import params. Define non-critical fields as optional in schema. Validate documents before import.","category":"schema","severity":"medium","description":"Typesense requires all defined fields in every document (unless field is optional). Missing a single field causes the entire document to be rejected.","last_verified":"2026-03-11T19:08:09.538851+00:00","evidence_count":1},{"pattern":"Node failover requires client-side configuration","impact":"Agent loses search capability when primary node goes down, even if cluster is healthy. No automatic reconnection to healthy nodes.","frequency":"rare","workaround":"Configure all cluster nodes in client initialization. Use nearest-node option for latency optimization. Implement health check pings to detect node failures.","category":"connection","severity":"medium","description":"Multi-node Typesense clusters require the client to know all node addresses. No automatic discovery. If primary node fails, agent must have fallback configured.","last_verified":"2026-03-11T19:08:09.538851+00:00","evidence_count":1}]},"error":null}