ruvnet/ruflo · error · Error

Maximum concurrent workflows reached

Error message

Maximum concurrent workflows reached

What it means

MaestroPlugin.executeWorkflow found the workflow but activeWorkflows is already at config.maxConcurrentWorkflows. A concurrency cap on orchestration: the workflow is valid, it simply cannot start until a running workflow finishes.

Source

Thrown at v3/@claude-flow/shared/src/plugins/official/maestro-plugin.ts:186

      createdAt: new Date(),
      checkpoints: new Map(),
    };

    this.workflows.set(workflow.id, workflow);
    return workflow;
  }

  /**
   * Execute a workflow
   */
  async executeWorkflow(workflowId: string): Promise<OrchestrationResult> {
    const workflow = this.workflows.get(workflowId);
    if (!workflow) {
      throw new Error(`Workflow not found: ${workflowId}`);
    }

    if (this.activeWorkflows >= this.config.maxConcurrentWorkflows) {
      throw new Error('Maximum concurrent workflows reached');
    }

    const startTime = Date.now();
    workflow.status = 'running';
    workflow.startedAt = new Date();
    this.activeWorkflows++;

    const errors: Array<{ stepId: string; error: string }> = [];
    const outputs: Record<string, unknown> = {};

    try {
      switch (this.config.orchestrationMode) {
        case 'sequential':
          await this.executeSequential(workflow, outputs, errors);
          break;
        case 'parallel':
          await this.executeParallel(workflow, outputs, errors);
          break;

View on GitHub (pinned to fa13ee4ad6)

Solutions

1. Raise the max concurrent workflow limit in configuration if needed.
2. Wait for running workflows to complete before starting new ones.

When it happens

Trigger: Thrown at v3/@claude-flow/shared/src/plugins/official/maestro-plugin.ts:186 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/9810ef5168fc1ad0. Report an issue: GitHub.