Session Serialization/Deserialization of Service Requestor
Hi,
We are working on a solution, that is using Pega's Stateful Service requestor for exposing the business layer.
We would like to know the following
1. Timeout for Service Requestor
2. How Session Serialization/Deserializationwould work for Service Requestor after the time out
Regards,
Sunil Darla
Pegasystems Inc.
GB
@SunilD71 For the timeout of a Service Requestor you can refer to the session management settings in Pega. The default timeout values for different requestor types are specified in the Session Management Troubleshooting FAQs. For example the default timeout for application requestors is 600 seconds (10 minutes). You can customize these settings by navigating to SysAdmin Requestor type and updating the value defined in the Requestor type. Regarding session serialization/deserialization after timeout when a requestor state becomes 'disconnected' (e.g. when the user closes the browser or the network connection is down) the requestor can be restored if the browser session is still alive. The default timeout setting for a disconnected requestor can be reviewed and changed as needed.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.