Applies to Pega Platform 7.2-8.7
This article provides answers to frequently asked questions about Requestor Management and troubleshooting issues with Requestor Management.
Introduction
You can manage active requestors across all nodes (current and remote) in a cluster through the Requestor Management landing page. You can view all the actions performed by a particular user and observe details related to actions such as application and Requestor type. You can also trace issues with Requestor activity.
For more information on the Requestor Management landing page and Managing requestors, read the following articles:
Answers to frequently asked questions
How to access the Requestor Management landing page?
To access the Requestor Management landing page, perform the following steps:
- Log in to the Admin Studio.
- Navigate to Resources > Requestors.
How to determine the Requestor ID of the current session from the Requestor Management landing page?
To determine the Requestor ID of the current session, click the Active tab of the Requestor Management landing page. The Requestor ID of the current session will be highlighted in Blue color.
What is the reason for the occurrence of the following error on terminating a browser requestor on the Requestor Management landing page:
‘Requestor HQIKV2W34PAW8I40IAHHBK1ADTA4NY5U4A is already terminated.’
D_pzRequestors is a thread-level data page that is used to store the information of the requestors present in a cluster. The data page loads while opening the Requestor Management landing page. Switching between different tabs does not reload the data page. The requestor might get destroyed when you attempt to terminate the browser requestor.
To address this issue, refresh the page by clicking Actions and selecting the Refresh option. Verify if the requestor is present in the Reloaded list.