Référence
Error codes
What Stratum's E: and M: error codes mean, and how to resolve them.
When something goes wrong, Stratum shows a short code you can look up or quote in a bug report. Codes come in two families.
Code format
E:…— an environment problem: something missing or misconfigured on the machine (Git, a path, permissions).M:…— a managed operation problem: Stratum tried an action (sync, import, restore) and it didn't complete.
E: — environment
| Code | Meaning | Fix |
|---|---|---|
| E:GIT_NOT_FOUND | The git command-line tool isn't on PATH. | Install Git and restart Stratum. |
| E:GIT_TOO_OLD | Git is below the minimum supported version. | Update Git to a current release. |
| E:PATH_UNREACHABLE | A folder or share can't be reached. | Reconnect the drive / remap the NAS path. |
| E:PERMISSION_DENIED | Stratum can't read or write a path. | Check folder permissions or pick another folder. |
| E:NOT_A_REPO | The folder isn't a Stratum space and couldn't be initialised. | Choose an empty or writable folder, then retry. |
M: — operations
| Code | Meaning | Fix |
|---|---|---|
| M:SYNC_FAILED | A push or pull didn't complete. | Check connectivity to the remote and try Sync now. |
| M:PUSH_REJECTED | The remote had newer changes. | Sync again — Stratum will pull, then push. |
| M:CLONE_FAILED | Joining a studio space failed. | Verify the remote URL and that you have read access. |
| M:IMPORT_FAILED | A file couldn't be copied into the space. | Check free space and permissions, then retry. |
| M:RESTORE_FAILED | Writing an old version back failed. | Ensure the file isn't locked by another app. |
| M:INDEX_FAILED | The index or thumbnails couldn't be rebuilt. | Try Settings → This space → Rebuild index. |
| M:MODEL_DOWNLOAD_FAILED | An Ollama model didn't download. | Check that Ollama is running, then retry the download. |
Reporting a problem
If a code persists, open an issue on GitHub with the code and what you were doing. Include the Stratum version from Settings → Help & about. See also Troubleshooting & FAQ.