Skip to content

feat: per-scenario timeout override; chat-agent-advanced gets 600s#2

Open
ericallam wants to merge 1 commit into
mainfrom
feat/per-scenario-timeout
Open

feat: per-scenario timeout override; chat-agent-advanced gets 600s#2
ericallam wants to merge 1 commit into
mainfrom
feat/per-scenario-timeout

Conversation

@ericallam

Copy link
Copy Markdown
Member

Summary

Scenarios can set a timeoutMs to override the global per-run default. The chat-agent-advanced scenario (sessions / HITL / sub-agents, the heaviest task) was hitting the 300s cap in both arms, so its result reflected the timeout rather than the skill. It now gets 600s and completes.

This came out of evaluating a trigger.dev change where the whole sweep was green except chat-agent-advanced, which timed out identically in both arms. With 600s it completes, and the with-skills arm passes both samples.

Scenarios can now set `timeoutMs` to override the global config default. The
chat-agent-advanced scenario (sessions/HITL/sub-agents, the heaviest task) was
hitting the 300s cap in both arms, so the run reflected the timeout, not the
skill. Bump it to 600s.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant