Skip to main content
Understanding Memvid error codes helps you quickly diagnose and resolve issues. All errors follow the format MVXXX where XXX is a three-digit code.

Error Code Quick Reference


Storage Errors

MV001 - CapacityExceeded

Your memory file has exceeded its storage capacity limit.
Cause: The .mv2 file has reached its maximum allowed size based on your plan tier. Error Message:
Solutions:
Plan Limits:

Authentication Errors

MV002 - TicketInvalid

Cause: The ticket’s Ed25519 signature doesn’t match, indicating tampering or corruption. Error Message:
Solutions:
Tickets are cryptographically signed. Never manually edit ticket strings.

MV003 - TicketReplay

Cause: Attempting to apply a ticket with a sequence number less than or equal to the current ticket. Error Message:
Solutions:

MV008 - ApiKeyRequired

An API key is required for this operation.
Cause: Attempting to use a feature that requires authentication without providing an API key. Error Message:
Solutions:

Index Errors

MV004 - LexIndexDisabled

Lexical (text) search is not enabled on this memory file.
Cause: Attempting to use mode: lex or mode: auto on a file without lexical indexing. Error Message:
Solutions:

MV005 - TimeIndexMissing

Time-based queries require a time index that is not present.
Cause: Using timeline queries or time filters on a file without time indexing. Error Message:
Solutions:

MV011 - VecIndexDisabled

Vector (semantic) search is not enabled on this memory file.
Cause: Attempting to use mode: sem or mode: auto without vector indexing. Error Message:
Solutions:

MV014 - VecDimensionMismatch

Cause: Attempting to search or insert with embeddings of a different dimension than what the vector index was built with. Error Message:
Solutions:
  1. Use consistent embedding models: Ensure you use the same embedding model for ingestion and search.
  1. Rebuild with correct embeddings: If you need to change models, rebuild the vector index.

Integrity Errors

MV006 - VerificationFailed

Cause: The file’s checksums don’t match, indicating corruption. Error Message:
Solutions:
Always maintain backups of important memory files. Corruption can occur from disk errors, interrupted writes, or software bugs.

MV012 - CorruptFile

Cause: Severe file corruption preventing basic operations. Error Message:
Solutions:

MV013 - IOError

Cause: File system operations failed, such as file not found, permission denied, or disk full. Error Message:
Solutions:
Ensure the file path is correct and you have read/write permissions to the directory.

Concurrency Errors

MV007 - FileLocked

The file is locked by another process.
Cause: Another process has an exclusive write lock on the file. Error Message:
Solutions:

Data Errors

MV009 - MemoryAlreadyBound

This memory file is already bound to a different memory ID.
Cause: Attempting to bind a file that’s already associated with another memory in the control plane. Error Message:
Solutions:

MV010 - FrameNotFound

The requested frame does not exist.
Cause: Referencing a frame ID that doesn’t exist in the file. Error Message:
Solutions:

Embedding Errors

MV015 - EmbeddingFailed

Cause: The embedding runtime is unavailable, the API key is missing or invalid, or the model is not accessible. Error Message:
Solutions:
  1. Check API key configuration:
  1. Use local embeddings:
  1. Check network connectivity if using external providers:
Local embedding models (BGE, Nomic, GTE) work offline and don’t require API keys. They’re bundled with the SDK.

Security Errors

MV016 - EncryptedFile

The file is encrypted and requires decryption.
Cause: Attempting to open an encrypted .mv2e capsule without providing the password. Error Message:
Solutions:
  1. Decrypt the file:
  1. Open encrypted file in SDKs:
Never commit passwords to version control. Use environment variables or secure secret management.

System Errors

MV999 - InternalError

Cause: Unexpected condition in the Memvid engine. Error Message:
Solutions:
  1. Report the bug: Include the full error message and stack trace
  2. Try again: Some transient errors resolve on retry
  3. Check disk space: Ensure sufficient storage available
  4. Update Memvid: Upgrade to the latest version

SDK Error Handling

Python

Node.js


Getting Help

Troubleshooting Guide

Step-by-step solutions for common issues

GitHub Issues

Report bugs or request features

Discord Community

Get help from the community

FAQ

Frequently asked questions