Overview #
Time Out Configuration controls what happens when a candidate becomes inactive.
It helps balance user flexibility with process reliability.
Why timeout settings are important #
- Prevents abandoned sessions from blocking operations
- Improves consistency in analytics and completion metrics
- Supports clear recovery/resume behavior
- Reduces confusion in long-running journeys
Core timeout decisions #
Inactivity window #
How long a candidate can pause before timeout applies.
Resume behavior #
What happens when they return:
- Continue from last step
- Re-authenticate
- Restart selected sections (if policy requires)
System side effects #
What should be logged or triggered on timeout:
- Internal status update
- Notification logic
- Escalation or follow-up workflow
Recommended approach #
- Set conservative defaults first
- Test with real candidate behavior
- Tune by journey length and complexity
- Keep timeout policy documented per Agent
Testing scenarios #
- Candidate pauses briefly and resumes
- Candidate returns after timeout boundary
- Candidate times out during critical actions (e.g., signing)
- Session recovery under poor connectivity
Common pitfalls #
- Timeout too short for long form flows
- Timeout too long for compliance-sensitive flows
- No clear UX message on return after timeout
- Missing distinction between inactivity and explicit exit