Help

Error codes

When LEMIA cannot do what you asked, it says so with a stable code of the form E-101. This page gives, for each code, what happened and what unblocks it.

The code appears in the application’s error window. The Understand button brings you here, straight to that code’s entry; the Copy details button puts the code and the technical information about the incident on the clipboard.

If the step given below is not enough, write to contact@lemia.ch quoting the code and the copied details: that is what makes it possible to answer without asking you to reproduce the problem. You can also use the contact form.

Contents

1xx

Connection and licence

E-101 — Workstation not connected to the LEMIA server

The application only works if this workstation has been seen by the LEMIA server within the last 24 hours. That window has elapsed, or the workstation was detached.

What unblocks it. Check that the computer is online, then follow the connection screen. If you have an enrolment token, enter it. Your current work is not lost.

E-102 — Control server unreachable

The application could not reach the LEMIA server that authorises a run. The workstation remains usable until the end of its 24-hour window.

What unblocks it. Try again in a few minutes. If it persists, check the Internet connection and the server address under Settings › Connection.

E-103 — Enrolment refused

The LEMIA server refused to enrol this workstation: unknown, already used or expired token, or workstation revoked by the operator.

What unblocks it. Ask your LEMIA contact for a new enrolment token and try again. If the problem persists, copy the technical details from the error window and write to contact@lemia.ch quoting the code.

E-104 — Subscription suspended

Your practice’s subscription is past due or cancelled: the server no longer opens a session for this workstation.

What unblocks it. Contact your LEMIA contact to restore the subscription. If the problem persists, copy the technical details from the error window and write to contact@lemia.ch quoting the code.

E-105 — Launch token refused

The local LEMIA service did not recognise this window as its own. This happens when an old window stayed open after an update.

What unblocks it. Close every LEMIA window, then start the application again.

E-106 — Request refused by the local service

The local LEMIA service only accepts requests coming from the application itself. This request came from another origin and was blocked.

What unblocks it. Restart the application. If you are using a browser, open LEMIA from the installed application.

E-107 — Internet connection lost

This computer lost its Internet connection while working. LEMIA waited for it to come back, checking every ten seconds, then stopped the turn after five minutes.

What unblocks it. Check the Wi-Fi or the network cable, then send your request again. Your documents and folders are untouched.

2xx

AI provider

E-201 — API key missing

No Infomaniak key is stored on this workstation and none was provided by the server. Without a key the AI cannot answer.

What unblocks it. Open Settings › API keys and enter your Infomaniak key and product ID. The built-in guide “Infomaniak API key” walks through each step.

E-202 — API key refused

Infomaniak rejected the key that was sent: it is invalid, revoked, or does not grant access to the AI product indicated.

What unblocks it. Check the key and the product ID under Settings › API keys. A key can be regenerated in the Infomaniak manager (Account › API tokens).

E-203 — AI saturated

Infomaniak limits the number of requests per minute for each key. The limit was reached; the application waited, then gave up.

What unblocks it. Wait a minute and try again. If it happens often, lower the number of simultaneous runs in Settings, or request an additional key.

E-204 — Product token ceiling reached

Your practice’s Infomaniak AI product has used up its token volume. This is not a temporary saturation: waiting a few minutes will not help.

What unblocks it. Raise the ceiling from the Infomaniak manager (AI product › Quotas): the counter only resets on its own at the product’s monthly renewal.

E-205 — AI unreachable or too slow

The call to the AI provider did not complete within the allowed time: dropped connection, slow network, or Infomaniak service temporarily unavailable.

What unblocks it. Check the Internet connection and try again. On a very long document, narrow the request or split it into several steps.

E-206 — Invalid response from the AI provider

Infomaniak answered with an error or with content the application could not read: rejected request, server-side failure, or model temporarily unavailable.

What unblocks it. Try again. If the error persists with the same model, pick another tier (Fast, Medium, Powerful) until the service recovers.

E-207 — Empty answer

The model finished without writing anything. This happens when its whole output budget is spent on reasoning, or when the request was silently declined.

What unblocks it. Rephrase and shorten the request, or try again with a more powerful tier.

E-208 — Run blocked: suspicious instruction detected

Before starting a run, LEMIA scans the documents provided. One of them contains text that looks like an instruction meant to hijack the AI (prompt injection). As a precaution, nothing was executed.

What unblocks it. Open the flagged document and check the suspicious passage. Remove it, or run without that document.

E-209 — Model not allowed in confidential mode

The agent was configured with a provider or model that does not process data in Switzerland. LEMIA refuses to use it and did not look for a substitute.

What unblocks it. Open the agent’s configuration and pick an Infomaniak model (Fast, Medium, Powerful).

E-210 — Answer cut by the output ceiling

The model reached the maximum number of words it can write in one call. The answer is incomplete, or a tool call was abandoned rather than executed halfway.

What unblocks it. Ask for the document in several parts, or narrow the request. For a long deliverable the assistant can build the file over several calls.

E-211 — AI provider error

The call to the AI provider failed for a reason the application cannot classify. The technical details give the service’s exact answer.

What unblocks it. Try again. If the problem persists, copy the technical details from the error window and write to contact@lemia.ch quoting the code.

3xx

Files and folders

E-301 — Path refused

The requested file or folder is outside the chosen work folders, or lies in a forbidden folder (red list in the Compliance space). LEMIA never touches it.

What unblocks it. Pick a file inside the agent’s work folders, or remove the folder from the red list under Compliance › Forbidden folders if that is intended.

E-302 — Working copy expired

Documents produced by the assistant but never saved are kept for 7 days, then deleted. This one no longer exists.

What unblocks it. Ask the assistant to produce it again, and this time click “Save”.

E-303 — File format not deliverable

The agent produced a file whose format is not in the list LEMIA agrees to hand over (office documents, PDF, text, code). It was not copied.

What unblocks it. Ask for the document in an office format (Word, Excel, PowerPoint, PDF, text).

E-304 — Document refused for its form

The file carries a document extension but its content does not match: embedded object, macro, external link or active field. LEMIA refuses to hand it over or open it.

What unblocks it. Ask the assistant to produce the document again without macros or embedded content.

E-305 — Folder not found or unreadable

A work folder no longer exists, was moved, or is not accessible with your rights (disconnected network drive, removed USB key).

What unblocks it. Check that the folder exists, then pick it again from the folders bar.

E-306 — Change ceiling reached

An agent cannot modify or delete more than 20 documents per turn, nor more than 50 per run. This ceiling protects your folders from a misread instruction.

What unblocks it. Split the work into several turns or runs. Changes already made are listed and reversible.

E-307 — Undo or restore impossible

LEMIA could not put the document back into its previous state: the backup copy is gone from the recycle folder, or the file is locked by another application.

What unblocks it. Close the document if it is open elsewhere, then try again. The folder’s .lemia-corbeille holds the last 14 days of copies.

E-308 — Upload impossible

The attached file could not be copied into the conversation’s workspace: unsupported format, file too large, or disk full.

What unblocks it. Check the file’s format and size, then attach it again.

E-309 — File picker unavailable

The system’s file or folder picker window could not open.

What unblocks it. Restart the application. If it persists, restart the computer.

E-310 — Open or save impossible

The file could not be opened or saved where requested: path not found, insufficient rights, or file locked by another application.

What unblocks it. Close the file if it is open elsewhere and check that the folder exists, then try again.

E-311 — Red list not read

The application could not re-read the list of forbidden folders (Compliance space). Until it is read, the screen does not modify it: saving from an empty screen would erase your forbidden folders.

What unblocks it. Reload the Compliance screen. If the error persists, check that the local service responds, then try again.

E-312 — Recycle folder unreadable

The .lemia-corbeille folder that keeps previous versions of your documents could not be read: insufficient rights, locked folder or unavailable disk. Your backups may still exist; the application simply cannot list them.

What unblocks it. Check that the work folder is accessible, then reopen the version history.

4xx

Execution

E-401 — Agent not found

The workflow names an agent type this version of LEMIA does not know. The workflow probably comes from a different version, or from a hand-edited file.

What unblocks it. Open the workflow, replace the affected step with a standard agent, then run again.

E-402 — Previous step failed

This agent was not started because a step it depends on failed. The cause lies in that step’s error.

What unblocks it. Fix the failed step (see its error), then rerun from it.

E-403 — Sharing between steps refused

An agent tried to read the output of a step it cannot access (same step, or a later one). LEMIA only shares the outputs of earlier steps.

What unblocks it. Check the order of steps in the workflow and move the agent after the ones it must read.

E-404 — Deliverable missing

The agent was expected to produce a file and did not, or announced it without writing it. Often it lacked a piece of information and asked for it in its answer.

What unblocks it. Read the agent’s answer: give it the missing information, or specify the expected format, then rerun.

E-405 — Validation impossible

The approved files could not be copied to the output folder: folder not found, insufficient rights, or a same-named file is locked.

What unblocks it. Check that the output folder exists and is not open elsewhere, then approve again.

E-406 — Run refused

The workflow’s pre-flight check refused to start: inconsistent configuration, work folder conflicting with the red list, or control server said no.

What unblocks it. Read the reason given in the details, fix the workflow’s configuration, then run again.

E-407 — The engine stopped

The program that runs the agents stopped before returning a result. The technical details give its last message.

What unblocks it. Try again. If the problem persists, copy the technical details from the error window and write to contact@lemia.ch quoting the code.

E-408 — Engine not found

The Python program bundled with LEMIA was not found on this workstation. The installation is incomplete or was altered (antivirus, disk cleanup).

What unblocks it. Reinstall LEMIA from the installer. Your local data is kept.

E-409 — Transcription impossible

The audio recording could not be transcribed: unrecognised format, file too long, or Infomaniak transcription service unavailable.

What unblocks it. Check the file (common formats: mp3, m4a, wav, under 24 MB) and try again.

E-410 — Instruction generation impossible

The AI could not write the requested instruction from your description.

What unblocks it. Rephrase the description in one or two concrete sentences, then try again.

E-411 — Error during the run

An agent failed for a reason the application cannot classify. The technical details give the exact message.

What unblocks it. Rerun the step. If the problem persists, copy the technical details from the error window and write to contact@lemia.ch quoting the code.

E-412 — Feature not available in this edition

This edition of LEMIA does not include the Workflows space: the requested feature is not yet offered on your workstation. Nothing was lost.

What unblocks it. Use the Agents space for this work. If the problem persists, copy the technical details from the error window and write to contact@lemia.ch quoting the code.

E-413 — Web access without a recorded consent

Web mode was requested, but this workstation has no valid acceptance of the notice (missing, expired after seven days, or from an earlier version). No search was sent and nothing left Switzerland.

What unblocks it. Re-enable web access (globe button) and accept the notice, then resend your request. If the problem persists, copy the technical details from the error window and write to contact@lemia.ch quoting the code.

5xx

Application

E-501 — The display hit an error

Part of the interface could not be drawn. Your local data (conversations, workflows, settings) is kept.

What unblocks it. Click “Retry”. If the screen fails again, reload the application.

E-502 — The interface could not start

The main screen failed before it could display. Your local data is kept.

What unblocks it. Click “Retry”, then restart the application if the error returns. If the problem persists, copy the technical details from the error window and write to contact@lemia.ch quoting the code.

E-503 — The local service does not start

Each time it opens, LEMIA starts a local service on your computer. It did not start or stopped immediately: port 3000 already used by another program, antivirus blocking the launch, or altered installation.

What unblocks it. Close other LEMIA windows and restart. If it returns, close the program using port 3000, check the antivirus, or reinstall LEMIA. The backend-spawn.log file in the application’s data folder gives the detail.

E-504 — Local service not identified

A program is listening on port 3000, but it is not the service LEMIA just started. For safety, the application refuses to connect to it.

What unblocks it. Close the program using port 3000 (often an old LEMIA window), then restart.

E-505 — Local data unreadable

Part of your local data is encrypted with a key this workstation no longer has, or its file is damaged. The application restarts from empty settings for that part, without erasing the file.

What unblocks it. If you switched Windows session or restored a profile, sign in with the original session. If the problem persists, copy the technical details from the error window and write to contact@lemia.ch quoting the code.

E-506 — Unexpected error

The application hit an error it did not anticipate. It keeps working; the action in progress may have been interrupted.

What unblocks it. Repeat the action. If the problem persists, copy the technical details from the error window and write to contact@lemia.ch quoting the code.

E-507 — Local saving suspended

The application could not encrypt your data to store it on this workstation: the local service no longer provides the encryption key. What you do stays on screen but is NOT saved while this message is shown.

What unblocks it. Copy what matters (the text of an answer, settings in progress), then restart the application. Saving resumes as soon as the key is available again.

E-508 — Consent log not written

Your acceptance (terms of use, web access) was applied on screen, but the application could not write it to the workstation’s audit log. Without that line, the proof of consent is missing from the compliance file.

What unblocks it. Restart the application and accept again: the line will be rewritten. If the problem persists, copy the technical details from the error window and write to contact@lemia.ch quoting the code.