Dashboard chat turns longer than two minutes are cut off client-side and fail with the browser text 'The operation was aborted'. The UI arms one 120 s timer per turn and only re-arms it for operator questions, so a tool-heavy turn that is making progress is aborted; the gateway records it cancelled with 'context canceled'. Following messages hit the same wall, so no model reply appears. The gateway does not log turn failures and the stored/shown error has no cause or last step. Done when: a turn that keeps producing events or runs one long silent tool is not aborted by client or proxy; a client timeout says no activity for N minutes; a failed or cancelled turn stores a real cause with the last completed step and the gateway logs it; task failure/park reasons are verified actionable.
Dashboard chat turns longer than two minutes are cut off client-side and fail with the browser text 'The operation was aborted'. The UI arms one 120 s timer per turn and only re-arms it for operator questions, so a tool-heavy turn that is making progress is aborted; the gateway records it cancelled with 'context canceled'. Following messages hit the same wall, so no model reply appears. The gateway does not log turn failures and the stored/shown error has no cause or last step. Done when: a turn that keeps producing events or runs one long silent tool is not aborted by client or proxy; a client timeout says no activity for N minutes; a failed or cancelled turn stores a real cause with the last completed step and the gateway logs it; task failure/park reasons are verified actionable.
Fixed in 074ebbd9: idle timer re-arms on every stream chunk, server keepalive every 15 s, timeout message names the last step, gateway logs turn failures and stores the last completed step in the turn error. Task view already shows park reason and failing stage; nothing to change.
Fixed in 074ebbd9: idle timer re-arms on every stream chunk, server keepalive every 15 s, timeout message names the last step, gateway logs turn failures and stores the last completed step in the turn error. Task view already shows park reason and failing stage; nothing to change.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Dashboard chat turns longer than two minutes are cut off client-side and fail with the browser text 'The operation was aborted'. The UI arms one 120 s timer per turn and only re-arms it for operator questions, so a tool-heavy turn that is making progress is aborted; the gateway records it cancelled with 'context canceled'. Following messages hit the same wall, so no model reply appears. The gateway does not log turn failures and the stored/shown error has no cause or last step. Done when: a turn that keeps producing events or runs one long silent tool is not aborted by client or proxy; a client timeout says no activity for N minutes; a failed or cancelled turn stores a real cause with the last completed step and the gateway logs it; task failure/park reasons are verified actionable.
Fixed in
074ebbd9: idle timer re-arms on every stream chunk, server keepalive every 15 s, timeout message names the last step, gateway logs turn failures and stores the last completed step in the turn error. Task view already shows park reason and failing stage; nothing to change.