scriptoriumadmin/Roo-Code
1
0
Fork 0
mirror of https://github.com/RooVetGit/Roo-Code.git synced 2026-08-28 05:27:24 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Fix #4896: Handle API streaming errors in subtasks properly

Browse source 
When an API streaming error occurs in a subtask, instead of reinitializing
the subtask with history (which keeps it stuck in subtask view), properly
return control to the parent task by calling finishSubTask().

This ensures that orchestrator mode can properly resume the parent task
after a subtask encounters an API streaming failure during cancellation.
This commit is contained in:
Roo Code 2025-06-19 18:34:57 +00:00
parent 2e2f83be60
commit dc3359a224
1 changed files with 10 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
src/core/task/Task.ts
View file

@ -1422,10 +1422,17 @@ export class Task extends EventEmitter<ClineEvents> {
error.message ?? JSON.stringify(serializeError(error), null, 2),
)
const history = await provider?.getTaskWithId(this.taskId)
// Check if this is a subtask - if so, return to parent instead of reinitializing
if (this.parentTask) {
// For subtasks, finish the subtask and return to parent
await provider?.finishSubTask(`API streaming error: ${error.message ?? "Unknown error"}`)
} else {
// For main tasks, reinitialize with history as before
const history = await provider?.getTaskWithId(this.taskId)
if (history) {
await provider?.initClineWithHistoryItem(history.historyItem)
if (history) {
await provider?.initClineWithHistoryItem(history.historyItem)
}
}
}
} finally {