Handling session timeout warnings for guest users on long Pega self‑service submissions

In my opinion, for a guest/self-service flow, I would not rely on extending the session too much. Pega’s guest requestors are intentionally short-lived, and the default idle timeout for guest requestors is about one minute.

What I would suggest is:

  • Auto-save partial progress frequently at each step/screen, so timeout does not mean data loss.

  • Show a client-side warning/countdown before expiry.

  • If the session ends, make sure the user can resume from a draft / saved case state.

1 Like