Mintplex-Labs/anything-llm · error
Document processing API is not online. Request will not be p
Error message
Document processing API is not online. Request will not be processed.
What it means
Availability guard in the raw-text embed API: the collector is offline, so the submitted raw text content cannot be processed and the request is rejected with a 500 instead of queuing unprocessable text.
Source
Thrown at server/endpoints/api/document/index.js:527
}
*/
try {
const Collector = new CollectorApi();
const requiredMetadata = ["title"];
const {
textContent,
metadata: _metadata = {},
addToWorkspaces = "",
} = reqBody(request);
const metadata =
typeof _metadata === "string"
? safeJsonParse(_metadata, {})
: _metadata;
const processingOnline = await Collector.online();
if (!processingOnline) {
return response
.status(500)
.json({
success: false,
error: `Document processing API is not online. Request will not be processed.`,
})
.end();
}
if (
!requiredMetadata.every(
(reqKey) =>
Object.keys(metadata).includes(reqKey) && !!metadata[reqKey]
)
) {
return response
.status(422)
.json({
success: false,
error: `You are missing required metadata key:value pairs in your request. Required metadata key:values are ${requiredMetadataView on GitHub (pinned to 3aec848f28)
Solutions
- Bring the document processing API online and retry the request.
- Check collector service logs and connectivity from the server.
Defensive patterns
Strategy: retry
When it happens
Trigger: Thrown at server/endpoints/api/document/index.js:527 when the library encounters an invalid state.
Common situations: Calling a document-processing endpoint while the collector service is not running or unreachable.
AI-assisted analysis of Mintplex-Labs/anything-llm@3aec848f28 (2026-08-18).
Data as JSON: /api/errors/af72588404dee749.
Report an issue: GitHub.