Answers
Every question is answered with “I don't know based on the available knowledge.”
Every question is answered with “I don't know based on the available knowledge.”
The assistant retrieves nothing it can answer from. Check, in order:
- Ingestion finished. Check the source’s latest job on the Knowledge page, or with Get a source’s current job. Questions asked before ingestion completes abstain.
- Documents landed. List documents for the collection. An empty list means the source produced nothing; check its URL, path filters and bounds.
- The assistant uses the right collection. Select Knowledge on the assistant’s row on the Assistants page, or get the assistant and compare
knowledge_base_idswith the collection you ingested into. - The content covers the question. If it does not, abstaining is the correct answer. See Content best practices.
Asking a question returns 400 “This assistant is not available to answer questions”
Asking a question returns 400 “This assistant is not available to answer questions”
The assistant has no knowledge attached, or its status is
disabled or archived. On the
Assistants page, select Knowledge on its row to attach a collection and Activate to
set it live, or send knowledge_base_ids and status to Update an
assistant.The model list is empty
The model list is empty
Your deployment has no model provider configured, so it can neither answer nor ingest. Contact
your MITHUNAI administrator.
Ingestion
An ingestion job fails or ingests fewer pages than expected
An ingestion job fails or ingests fewer pages than expected
- The site may be unreachable from MITHUNAI, or slower than the fetch timeouts allow.
- The crawl may have reached its depth or page limit. Raise
max_depthormax_pageswithin the allowed range, or use a sitemap. - Include and exclude patterns may be filtering out the pages you want.
- URLs that resolve to private or internal network addresses are refused by design.
API errors
401 authentication_error with an API key
401 authentication_error with an API key
The key is missing, mistyped, revoked or expired, or was truncated when copied. The secret is
shown only once, so if in doubt, create a new key and revoke the old one. Send it as
Authorization: Bearer arukz_sk_….404 not_found for something that exists
404 not_found for something that exists
The resource belongs to a different organisation from the one your credential acts in. Resources
in other organisations are reported as not found by design.
409 conflict when asking a question
409 conflict when asking a question
The conversation is still answering a previous question. A conversation handles one question at a
time; wait for the first to finish, or start another conversation.
429 rate_limit_exceeded
429 rate_limit_exceeded
Wait for the number of seconds in the
Retry-After header, then retry. If many users share one
office network, they share one budget before authentication; see Rate
limits.The widget
The widget does not appear on my page
The widget does not appear on my page
Open the browser’s developer console:
- A message from the widget names the configuration problem, such as a missing
apiBaseUrlor a key that does not start witharukz_wk_. - A CORS error means your page’s origin is not allowed. It must be in both the embed’s allowed origins and your deployment’s allowlist, spelled exactly, for example
https://docs.example.comwith no trailing slash.https://example.comandhttps://www.example.comare different origins. - No request at all usually means the snippet is missing or was edited. Copy it again from Operations → Widget embeds and paste it unchanged; see the widget guide.
- The embed was revoked. Revocation is permanent; create a new embed.
The widget appears, but every question fails with 400
The widget appears, but every question fails with 400
The assistant the embed uses cannot answer: it is
disabled or archived, or has no knowledge
attached. On the Assistants page, select Activate and Knowledge on its row, or use
Update an assistant. An embed’s assistant cannot be
changed; to use a different one, create a new embed.A widget conversation disappeared
A widget conversation disappeared
Widget conversations belong to the browser tab that started them and end when the tab closes. This
is deliberate, so shared computers do not reveal one visitor’s questions to the next.
Streaming and CORS
Streaming pauses, then shows the whole answer at once
Streaming pauses, then shows the whole answer at once
A proxy between your client and MITHUNAI is buffering the response. Configure it not to buffer
text/event-stream responses and to pass the X-Accel-Buffering: no header through.A streamed request returned 200 but no answer
A streamed request returned 200 but no answer
On a streaming request,
200 only means the stream opened. Read the final event:
answer.completed, answer.interrupted or answer.error. See
Streaming.Browser calls to the API fail with a CORS error
Browser calls to the API fail with a CORS error
Expected. Apart from the widget endpoints, the API does not accept cross-origin browser requests. Call it from your backend. See HTTP API.
Still stuck?
Contact your MITHUNAI representative with the endpoint, the time, the errorcode, and the conversation or job ID involved. Never include API keys or other secrets.