Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Stateless processing and pooling for service packages

Updated on April 6, 2022

Stateless processing and requestor pooling are appropriate when the client (calling) system handles security, transactions, workflows, and similar aspects of the interface.

Note: If your application is deployed on Kubernetes, the Pooling tab on the service package rule form is unavailable.
When you choose Stateless as the processing mode, Pega Platform performs the following actions at run time:
  • Creates additional requestors only as needed and retains them for reuse, based on information in the Pooling tab.
  • Selects the appropriate access group, depending on your configuration:
    • If you select Requires authentication on the Context tab of the service package, the system uses the default access group of the authenticated operator as the context.
    • If you do not select Requires authentication on the Context tab, the system uses the access group that is defined on the service package.

For more information, see Service package access group.

You can monitor the operation of a requestor pool using the Administration > Requestor Pools menu item of the System Management application.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us