ruvnet/ruflo · error · BdBridgeError
TIMEOUT
TIMEOUT
Error message
Command execution timed out
What it means
The spawned bd process was killed before finishing — the command exceeded the configured timeout, so the bridge kills it and raises a TIMEOUT-coded BdBridgeError. The command, its args, and duration are attached for diagnosis; lengthen the timeout or use a narrower query.
Source
Thrown at v3/plugins/gastown-bridge/src/bridges/bd-bridge.ts:508
durationMs,
};
// Cache successful results
if (isCacheable && result.success) {
staticCache.set(cacheKey, result);
}
return result;
} catch (error: unknown) {
const durationMs = Date.now() - startTime;
const err = error as NodeJS.ErrnoException & {
killed?: boolean;
stdout?: string;
stderr?: string;
};
if (err.killed) {
throw new BdBridgeError(
'Command execution timed out',
'TIMEOUT',
'bd',
validatedArgs
);
}
if (err.code === 'ENOENT') {
throw new BdBridgeError(
`bd executable not found at: ${this.config.bdPath}`,
'COMMAND_NOT_FOUND',
'bd',
validatedArgs
);
}
return {
success: false,View on GitHub (pinned to fa13ee4ad6)
Solutions
- Increase the configured timeout for long-running operations, or split the work into smaller units.
- Retry with exponential backoff; if persistent, inspect the downstream service for stalls.
Defensive patterns
Strategy: retry
When it happens
Trigger: Thrown at v3/plugins/gastown-bridge/src/bridges/bd-bridge.ts:508 when the library encounters an invalid state.
Common situations: See trigger scenarios.
Understand the failure class
- Timeouts: ETIMEDOUT, deadlines, and hung requests — what actually expires when a request times out.
AI-assisted analysis of ruvnet/ruflo@fa13ee4ad6 (2026-08-18).
Data as JSON: /api/errors/d3f6ae9a52842293.
Report an issue: GitHub.