ruvnet/ruflo · error

[mcp] flow failed, falling back to default endpoint

Error message

[mcp] flow failed, falling back to default endpoint

What it means

Log warning in runMcpFlow: an exception escaped the MCP generation loop (and was not a user abort); the flow is abandoned and generation falls back to the default (non-MCP) endpoint.

Source

Thrown at ruflo/src/ruvocal/src/lib/server/textGeneration/mcp/runMcpFlow.ts:824

				{ length: lastAssistantContent.length, loop },
				"[mcp] final answer emitted (no tool_calls)"
			);
			return "completed";
		}
		logger.warn({}, "[mcp] exceeded tool-followup loops; falling back");
	} catch (err) {
		const msg = String(err ?? "");
		const isAbort =
			(abortSignal && abortSignal.aborted) ||
			msg.includes("AbortError") ||
			msg.includes("APIUserAbortError") ||
			msg.includes("Request was aborted");
		if (isAbort) {
			// Expected on user stop; keep logs quiet and do not treat as error
			logger.debug({}, "[mcp] aborted by user");
			return "aborted";
		}
		logger.warn({ err: msg }, "[mcp] flow failed, falling back to default endpoint");
	} finally {
		// ensure MCP clients are closed after the turn
		await drainPool();
	}

	return "not_applicable";
}

View on GitHub (pinned to fa13ee4ad6)

Solutions

1. Inspect the underlying MCP flow error logged before this message; fix the MCP server connection, tool listing, or model response causing the flow to fail.

When it happens

Trigger: Thrown at ruflo/src/ruvocal/src/lib/server/textGeneration/mcp/runMcpFlow.ts:824 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of ruvnet/ruflo@fa13ee4ad6 (2026-08-18). Data as JSON: /api/errors/6200ceba80cb94f4. Report an issue: GitHub.