ruvnet/ruflo · error · QECoreError

Failed to wait for task

Error message

Failed to wait for task

What it means

Wraps any failure of taskService.waitForCompletion (backend unavailable, task crashed, lost task) into a QECoreError so callers get a uniform bridge error with the original cause attached; the task handle's status is left unchanged.

Source

Thrown at v3/plugins/agentic-qe/src/bridges/QECoreBridge.ts:547

  }

  async wait(): Promise<TaskResult> {
    try {
      this.logger.debug(`Waiting for task completion: ${this.id}`);
      const result = await this.taskService.waitForCompletion(this.id);

      this._status = result.success ? 'completed' : 'failed';

      return {
        taskId: this.id,
        success: result.success,
        data: result.data,
        error: result.error,
        durationMs: result.durationMs,
      };
    } catch (error) {
      this.logger.error(`Failed to wait for task: ${this.id}`, error);
      throw new QECoreError('Failed to wait for task', error as Error);
    }
  }

  async cancel(): Promise<void> {
    try {
      this.logger.debug(`Cancelling task: ${this.id}`);
      await this.taskService.cancel(this.id);
      this._status = 'cancelled';
    } catch (error) {
      this.logger.error(`Failed to cancel task: ${this.id}`, error);
      throw new QECoreError('Failed to cancel task', error as Error);
    }
  }

  async getProgress(): Promise<TaskProgress> {
    try {
      const status = await this.taskService.getStatus(this.id);
      this._status = status.status;

View on GitHub (pinned to fa13ee4ad6)

Solutions

1. Verify the task id and that the task is still tracked.
2. Handle task timeout separately from transport failure.

When it happens

Trigger: Thrown at v3/plugins/agentic-qe/src/bridges/QECoreBridge.ts:547 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/0a05163b52b1f9ef. Report an issue: GitHub.