Troubleshooting
MitDesk often stops on purpose. Most "faults" are a refusal with a reason. This page lists messages that exist in the product today, what they mean, and how to fix them. A call that waits for a person is not a fault. It is consent at work, and it waits in Decisions.
The Why it stopped column of Configuration ▸ What has run ▸ Jobs shows the reason a job stopped.
Nothing answers, or answers never start
Open Settings and find the block Turn worker, setting Who runs the turns. A green line says the turn worker ran in the last five minutes. A red box titled Nothing is running agent turns. gives one of two reasons:
This server runs no cron threads (max_cron_threads=0), so no agent turn will ever run. Start Odoo with max_cron_threads of at least 1 (4 is the requirement for MitDesk) and try again.
MitDesk's turn worker has not run for 7 minutes. The server's cron workers are either stopped or all busy: check that Odoo runs with cron threads and that no other job holds them.
Agent turns run on Odoo's cron workers. Set max_cron_threads = 4 in odoo.conf and restart Odoo. Settings also say limit_time_real_cron = 900.
Long answers stop early
A yellow box in the same block says This server ends long turns early. It names the agents that may work longer than the server allows, and ends with a fix:
An administrator has to set limit_time_real_cron = 900 in odoo.conf and restart Odoo.
If the server limit is too low, a turn may also end with this message in the chat:
MitDesk lost the worker that was running this turn. This server ends a background worker after 120 s (limit_time_real_cron in odoo.conf), and this agent may work for 600 s, so the server most likely ended this turn. Sending the message again will probably end the same way.
Raise limit_time_real_cron as the message says. If it names a limit above 1800 seconds, lower the agent's max_wallclock_seconds instead. If the message ends with "the server stopped or restarted it. Please retry.", the worker was stopped for another reason. Send the message again.
The model is not set up
Chat and employees check the model before they call it. The message names the provider and where to fix it:
| Message | Fix |
|---|---|
MindDesk has no API key for Anthropic. Add it under Settings > MindDesk > AI keys, then try again. |
Add the key and press Test. A user who is not an administrator is told to ask one. |
Ollama is not answering at http://localhost:11434. Start it, or correct its address under Settings > MindDesk > AI keys, then try again. |
Start the server or fix the address. Only administrators see the address. Others read "is not answering on this server. Ask a MitDesk administrator to start it". |
MindDesk has no address for OpenAI-compatible endpoint. Add the server under Settings > MindDesk > AI keys > Manage AI endpoints and pick it on the model, then try again. |
Add the endpoint, then choose it on the AI Models record. |
Anthropic refused the API key -- check the API key under Settings > MindDesk > AI keys; the Test button there says whether it is accepted -- then try again. |
Replace the key. |
The OpenAI key is accepted but not allowed to use the model gpt-x. |
Use a model the key may use. |
OpenAI does not know the model id gpt-x. Check the technical id on the model. |
Correct the technical id on the model. |
Nothing answered at the Mistral address -- check the endpoint ... and the network, then try again. |
Check the network and the address. |
MindDesk: this model is not linked to an endpoint. Pick one on the model before using it. |
Choose an endpoint on the model. |
The 'openai' Python package is not installed, so MindDesk cannot reach this provider. Install it ... (pip install openai) and restart the server. |
Install the package for the Python that Odoo uses. The package is anthropic, openai or ollama, depending on the provider. |
The answer is empty or cut short
The model record has Max Tokens, with a default of 1024. For OpenAI models whose id starts with o1, o3, o4 or gpt-5, thinking uses tokens from the same allowance. A model can spend all of it thinking and show no text.
Raise Max Tokens on the model in AI Models. You can also set the agent's response style to Fast, which asks for low effort. For some Anthropic models with extended thinking, MitDesk adds room for the answer on top of the thinking budget.
The key is refused because of the host
MitDesk refuses to send the Office AI server key to 192.168.10.20: that host is not on the endpoint allowlist. If this address is yours, add it to the 'minddesk.endpoint_allowlist' system parameter.
MitDesk checks the host at the moment it attaches the key, not when you save the address. This catches an address that came from a restored dump or a hand edit.
Built-in hosts are api.openai.com, api.anthropic.com, generativelanguage.googleapis.com, api.mistral.ai, api.groq.com, openrouter.ai and api.deepseek.com. Loopback addresses such as 127.0.0.1 are allowed. A private address such as 10.0.0.5 is not. Add your host to the system parameter minddesk.endpoint_allowlist, separated by commas or new lines. The message shows the host only, never the full address.
The monthly AI budget is reached
MitDesk has reached this company's AI budget for the month (50.00 of 50.00 USD). Paid providers are paused until the budget is raised or the month rolls over; locally hosted models still answer.
Raise Monthly AI budget (USD) in Settings, block AI spend, or switch the agent to a local model. 0 means no ceiling.
A task stopped after some approvals
I stopped this request after 3 approval requests, which is the limit set for a single task. Nothing further was done and nothing was decided on your behalf — the next step still needs your approval. ...
One request may ask a person only a few times (3 by default). Send the rest as a new message. The message says you can raise the limit in Settings, but there is no field for it. An administrator sets it in the system parameter minddesk.max_gate_questions_per_run. 0 means no limit.
A job in the Jobs list may also say TOCTOU: target changed after approval — reconfirm required. The record changed after you approved, so MitDesk asks again. After two new requests it stops with target kept changing after approval. Check the record and ask again.
A run-as account is refused
When you pick the account an agent, flow or digital employee runs as, you may see:
MindDesk: an agent may not run as an administrator. Pick a dedicated internal user with only the access it needs.MindDesk: a flow cannot run as a portal user.MindDesk: the run-as account needs MindDesk user rights before an agent can act as it.- also: superuser or OdooBot, and archived account.
Choose a normal internal user with the MitDesk user group. The account is the ceiling of what the AI may do.
A digital employee stops running
The employee is Active, the schedule passes, and nothing happens. Open the employee. The field Why it was skipped names the reason. Common reasons:
Outside configured working hours.the run-as account 'Name' has been archived, ornow has administrator access, orno longer has MindDesk user rights.- No model, no API key, no address, or a local server that does not answer (see above).
After three identical obstacles in a row the employee pauses itself and posts: Paused after 3 scheduled runs met the same obstacle ... Resume once it is fixed. Fix the cause and press Resume. Queued work was held, not lost. Over the monthly budget, the run is skipped and the supervisor is told once a month. See Pause, hand over, retrain, fire.
A tile says denied, not zero
A dashboard tile is in one of four states: a value, no data, denied or error. Denied means the read was refused: by Odoo access rights, a record rule, or an autonomy rule for that read tool. It is not zero. Fix the access or the rule.
On the 360 board, a denied card names the app. A card that is missing means the bridge is not installed, or an autonomy rule refuses that read.
A sovereign refusal
Three refusals can stop a request for data-residency reasons. They apply to chat, flows, employees and MCP alike. See Sovereign routing.
- Sovereign Mode:
MindDesk Sovereign Mode is active: 'GPT' runs on a us_cloud provider, which is not allowed. Choose a local model, or ask an administrator to review the mode. - Data classes:
MindDesk data-classification routing blocked this turn: data classified as financial may not be sent to a us_cloud provider. Use a local model, or ask an administrator to review the routing matrix or configure a narrow Routing Allowance.Sometimes the message lists what lifts the block instead. - Cloud deny list:
MindDesk egress blocked: Contact may not be sent to a cloud provider. If the chat history holds the data, the message says so and gives ways out, such as starting a new chat.
All three write an entry in the audit log, even though the request fails. It holds a hash, not the text. The Check configuration button in Settings, block Sovereign Mode, lists the models the mode would refuse. It sends nothing out.
"Requires MitDesk Pro (not installed)"
In Settings, block Knowledge and semantic search, this line means minddesk_pro is not installed. Install it to search company knowledge. It is part of the Pro edition.
A module will not install
minddesk_sale needs the MitDesk base module at version 20.0.3.15.13 or newer, and found 20.0.3.10.0. Update MitDesk first, then install minddesk_sale.
Update minddesk, then install the module. Another message says a module is built for MitDesk on a different Odoo version. Install the release made for your Odoo version. minddesk_helpdesk and minddesk_voip also need Odoo Enterprise apps.
An outside AI client gets "endpoint disabled"
The MCP server answers with error -32000, endpoint disabled, and HTTP status 503, when the system parameter minddesk.mcp_enabled is False. Set it to True to switch the server on again. Business edition.
Mail tools say linking needs MailDesk Pro
Linking an email to an Odoo record needs the MailDesk Pro edition, which is where the link table lives. ... this is an edition boundary, not an empty result.
Install MailDesk Pro, or work without links. Other mail tools say a licence is not active ("this is not an empty inbox"), or that you are not a member of any mailbox. A mailbox administrator gives you access.
Related
Need help?
If this page does not solve your problem, contact us and include: your Odoo version, where Odoo is hosted, the page and the step where it went wrong, the exact message, and a screenshot with private data hidden. Never send passwords, API keys or tokens.