root/fusion
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: decouple stuck detector timeout

Browse Source
This commit is contained in:
Berlin Luk
2026-05-11 00:11:23 +08:00
parent 873154f82a
commit 7f87ff05f1
6 changed files with 23 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
packages/engine/src/stuck-task-detector.ts
View File

@@ -11,9 +11,8 @@
* - `recordProgress(taskId)` — step transitions (in-progress, done, skipped); resets counters
*
* The detector polls at a configurable interval and compares timestamps against
* `taskStuckTimeoutMs` from settings. When that explicit override is unset, the
* detector falls back to `workflowStepTimeoutMs` so in-flight tool calls cannot
* leave an in-progress task unmonitored by default.
* `taskStuckTimeoutMs` from settings. Project defaults keep this active by
* default while keeping workflow-step execution timeouts independent.
*/
import type { TaskStore, Settings } from "@fusion/core";
@@ -472,8 +471,8 @@ export class StuckTaskDetector {
// Defensive fallback for pause windows where lifecycle hooks haven't run yet.
if (settings.globalPause || settings.enginePaused) return;
const timeoutMs = settings.taskStuckTimeoutMs ?? settings.workflowStepTimeoutMs;
if (!timeoutMs || timeoutMs <= 0) return; // Disabled only when both stuck and workflow timeouts are unset/disabled
const timeoutMs = settings.taskStuckTimeoutMs;
if (!timeoutMs || timeoutMs <= 0) return; // Disabled when task stuck timeout is explicitly unset/disabled
const stuckTasks: string[] = [];