ruvnet/ruflo · error · Error
Task execution failed
Error message
Task execution failed
What it means
executeTask() threw while running the task under an assigned agent (agent crashed, tool failure, or timeout). runWorkflow catches per-task failures and rethrows with this generic message; consult the task's entry in the workflow event log for the underlying cause.
Source
Thrown at v3/src/task-execution/application/WorkflowEngine.ts:414
if (nestedResult.status === 'failed') {
throw new Error(`Nested workflow failed`);
}
} else {
// Get assigned agent or distribute
let agentId = task.assignedTo;
if (!agentId) {
const agents = await this.coordinator.listAgents();
const suitable = agents.find(a => a.canExecute(task.type));
agentId = suitable?.id;
}
if (!agentId) {
throw new Error(`No agent available for task ${task.id}`);
}
const result = await this.executeTask(task, agentId);
if (result.status === 'failed') {
throw new Error(result.error || 'Task execution failed');
}
}
const endTime = Date.now();
execution.taskTimings[task.id] = {
start: startTime,
end: endTime,
duration: endTime - startTime
};
completedTasks.add(task.id);
execution.state.completedTasks.push(task.id);
execution.executionOrder.push(task.id);
this.eventBus.emit('workflow:taskComplete', {
workflowId: workflow.id,
taskId: task.id
});View on GitHub (pinned to fa13ee4ad6)
Solutions
- Inspect the task's underlying error and logs; fix the failing step and retry the task.
- Add per-step error capture so the failing step's diagnostic is propagated to the caller.
Defensive patterns
Strategy: try-catch
When it happens
Trigger: Thrown at v3/src/task-execution/application/WorkflowEngine.ts:414 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/a08eb5b855b80f5c.
Report an issue: GitHub.