Mintplex-Labs/anything-llm · error

Workspace thread does not exist.

Error message

Workspace thread does not exist.

What it means

Existence guard in validWorkspaceAndThreadSlug middleware: the workspace resolved but no WorkspaceThread matches the threadSlug for this user and workspace, so the thread param is invalid and a 404 is returned.

Source

Thrown at server/utils/middleware/validWorkspace.js:41

async function validWorkspaceAndThreadSlug(request, response, next) {
  const { slug, threadSlug } = request.params;
  const user = await userFromSession(request, response);
  const workspace = multiUserMode(response)
    ? await Workspace.getWithUser(user, { slug })
    : await Workspace.get({ slug });

  if (!workspace) {
    response.status(404).send("Workspace does not exist.");
    return;
  }

  const thread = await WorkspaceThread.get({
    slug: threadSlug,
    user_id: user?.id || null,
    workspace_id: workspace.id,
  });
  if (!thread) {
    response.status(404).send("Workspace thread does not exist.");
    return;
  }

  response.locals.workspace = workspace;
  response.locals.thread = thread;
  next();
}

module.exports = {
  validWorkspaceSlug,
  validWorkspaceAndThreadSlug,
};

View on GitHub (pinned to 3aec848f28)

Solutions

1. Check the thread slug in the URL matches an existing thread in the given workspace.
2. Verify the thread belongs to the requesting user (in multi-user mode threads are per-user).

When it happens

Trigger: Request referenced a workspace thread that does not exist. Triggered when validWorkspace middleware cannot find the thread slug within the workspace (validWorkspace.js:41).

Common situations: See trigger scenarios.

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