ruvnet/ruflo · error

Condition not met within timeout

Error message

Condition not met within timeout

What it means

waitFor polled the condition function every interval ms until the timeout elapsed and it never returned truthy (thrown errors were swallowed and treated as not-yet). This is the generic wait-for-condition timeout: the awaited async state simply never became true within the deadline.

Source

Thrown at v3/@claude-flow/testing/src/helpers/test-utils.ts:38

    timeout = 5000,
    interval = 50,
    timeoutMessage = 'Condition not met within timeout',
  } = options;

  const startTime = Date.now();

  while (true) {
    try {
      const result = await condition();
      if (result) {
        return result;
      }
    } catch (error) {
      // Condition threw, continue waiting
    }

    if (Date.now() - startTime >= timeout) {
      throw new Error(timeoutMessage);
    }

    await sleep(interval);
  }
}

/**
 * Options for waitFor utility
 */
export interface WaitForOptions {
  timeout?: number;
  interval?: number;
  timeoutMessage?: string;
}

/**
 * Wait until a value changes
 *

View on GitHub (pinned to fa13ee4ad6)

Solutions

1. Increase the waitFor timeout if the condition legitimately takes longer.
2. Fix the system under test so the condition becomes true, or correct the predicate.

When it happens

Trigger: Thrown at v3/@claude-flow/testing/src/helpers/test-utils.ts:38 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/28f3a2ab8f21ff7d. Report an issue: GitHub.