Agentforce enforces a 120-second (2-minute) maximum response time
per agent turn. If the agent doesn't complete its reasoning, tool calls, and response generation within that window, the session times out the error message leaving no trace in the STDM.
What we've checked:
- No timeout text in ErrorMessageText or OutputValueText
- AiAgentSessionEndType is NOT_SET for every session, so it's not usable
- Step durations show no spike near 120s; the killed step appears not to be recorded
Current approach: infer timeouts per interaction as "user Input with no agent Output." Complication: Output messages outnumber Inputs ~2:1, so welcome or progress messages may hide real timeouts.
Questions:
- Is there any STDM field or event that records a turn-level timeout?
- How are others separating timeouts from user abandonment?
- Is a timeout signal on the roadmap for Session Tracing?
#Data360
This is where I’d avoid relying on message counts alone. With welcome/progress messages, Input → Output isn’t a reliable indicator of a completed turn.
I’d correlate the interaction ID across STDM and channel/API logs, then classify it as completed, abandoned, or suspected timeout. The bigger gap here is really observability at the agent-turn level.