Mintplex-Labs/anything-llm · error

Router not found.

Error message

Router not found.

What it means

Lookup miss in the GET /model-routers/:id admin endpoint: ModelRouter.getWithRulesAndCount returned null for the numeric id, meaning no model router row exists with that id, so a 404 with a null router is returned.

Source

Thrown at server/endpoints/modelRouter.js:40

      } catch (e) {
        console.error(e);
        response.sendStatus(500);
      }
    }
  );

  app.get(
    "/model-routers/:id",
    [validatedRequest, flexUserRoleValid([ROLES.admin])],
    async (request, response) => {
      try {
        const { id } = request.params;
        const router = await ModelRouter.getWithRulesAndCount({
          id: Number(id),
        });
        if (!router) {
          response
            .status(404)
            .json({ router: null, error: "Router not found." });
          return;
        }
        response.status(200).json({ router });
      } catch (e) {
        console.error(e);
        response.sendStatus(500);
      }
    }
  );

  app.post(
    "/model-routers/new",
    [validatedRequest, flexUserRoleValid([ROLES.admin])],
    async (request, response) => {
      try {
        const user = await userFromSession(request, response);
        const data = reqBody(request);

View on GitHub (pinned to 3aec848f28)

Solutions

1. Verify the router ID or name exists before referencing it.
2. List configured routers and use a valid identifier.

When it happens

Trigger: Thrown at server/endpoints/modelRouter.js:40 when the library encounters an invalid state.

Common situations: Referencing a model router that has not been created or was deleted.

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