Mintplex-Labs/anything-llm · error

reason || "No document returned from collector"

Error message

reason || "No document returned from collector"

What it means

Propagation guard in the parse endpoint: the collector call returned success=false or no document object, meaning parsing was rejected or produced nothing; the collector's reason (or a no-document fallback) is returned as the error.

Source

Thrown at server/endpoints/workspacesParsedFiles.js:147

    async function (request, response) {
      try {
        const user = await userFromSession(request, response);
        const workspace = response.locals.workspace;
        const Collector = new CollectorApi();
        const { originalname } = request.file;
        const processingOnline = await Collector.online();

        if (!processingOnline) {
          return response.status(500).json({
            success: false,
            error: `Document processing API is not online. Document ${originalname} will not be parsed.`,
          });
        }

        const { success, reason, documents } =
          await Collector.parseDocument(originalname);
        if (!success || !documents?.[0]) {
          return response.status(500).json({
            success: false,
            error: reason || "No document returned from collector",
          });
        }

        // Get thread ID if we have a slug
        const { threadSlug = null } = reqBody(request);
        const thread = threadSlug
          ? await WorkspaceThread.get({
              slug: String(threadSlug),
              workspace_id: workspace.id,
              user_id: user?.id || null,
            })
          : null;
        const files = await Promise.all(
          documents.map(async (doc) => {
            const metadata = { ...doc };
            // Strip out pageContent

View on GitHub (pinned to 3aec848f28)

Solutions

1. Inspect the collector logs for the parse of this file — the collector returned success=false or no documents.
2. Verify the file type is supported by the collector and the file is not corrupted or empty.
3. Re-upload the file and retry parsing; check that the collector has write access to its storage/hotdir.

When it happens

Trigger: The collector returned no document for a parse request. Triggered when the collector responds without document content (or an explicit reason) for a parsed file in workspacesParsedFiles.

Common situations: See trigger scenarios.

AI-assisted analysis of Mintplex-Labs/anything-llm@3aec848f28 (2026-08-18). Data as JSON: /api/errors/1a620e0cb4cd1b65. Report an issue: GitHub.