# Agent9 Router Assignment Time Budget

<!-- auto-oncall-optimization-record
{
  "schemaVersion": "auto-oncall-optimization-record-v1",
  "optimizationId": "agent9-router-assignment-time-budget-2026-08-24",
  "problems": [
    {
      "problemId": "agent9-router-assignment-timeout",
      "summary": "The Agent9 Scenario Router assignment Turn shared a 60-second stage budget with Session readiness and initial workspace synchronization, leaving less than the intended reasoning time and interrupting TCID-13071 before a route was returned.",
      "status": "optimized_verified",
      "applicability": "Agent9-backed Auto-oncall diagnostic Scenario Router assignment Turns.",
      "issueKeys": ["TCID-13071"],
      "sourceRefs": ["agent9-session:sess_f1147f5da91746378a58e425bb5ffe15#problem:router-assignment-timeout"],
      "signalTextIncludesAny": [
        "agent9 router assignment timeout",
        "scenario router interrupted before route"
      ],
      "observedThrough": "2026-08-24",
      "effectiveAt": "2026-08-24T08:59:00Z",
      "verifiedAt": "2026-08-24T09:30:25Z",
      "attemptedAction": "Increase only the Scenario Router assignment stage cap from 60 seconds to 120 seconds; the existing pipeline budget still includes Session readiness and workspace synchronization.",
      "evidenceUrl": "https://internal.us-west-2.agent.mem9.ai/api/sessions/sess_29cbaff2c0a545bea7fd3a139e375d47"
    }
  ]
}
-->

- Optimization ID: `agent9-router-assignment-time-budget-2026-08-24`
- Owner: Auto-oncall Scenario Router assignment stage
- Source: TCID-13071 Agent9 Session `sess_f1147f5da91746378a58e425bb5ffe15`
- Implementation status: deployed
- Effective status: `optimized_verified`

## Bounded problem

The initial Scenario Router assignment had a 60-second cap. The cap begins before
the Agent9 Turn and therefore includes Session Drive readiness, initial workspace
sync, Turn admission, and model execution. The observed TCID-13071 Router was
interrupted without returning a route.

## Candidate change

Raise only the assignment cap to 120 seconds. Keep Router reconciliation at its
existing independent cap and keep the total pipeline deadline unchanged.

## Verification evidence

Read-only run `a64e970a-c16f-410e-ad27-824c8012ba13` created Router Session
`sess_29cbaff2c0a545bea7fd3a139e375d47`. Its assignment Turn completed in
35.705 seconds and Router reconciliation reused the same Session. The run
returned `status=ok`; the old pre-route 60-second interruption did not recur.

## Unresolved gaps

- This record does not own later Evidence or Final Response timeouts.

## Next validation action

Preserve the 120-second assignment cap and continue measuring it separately from
the ticket-level diagnostic deadline.