Unable to Trace Queue Processor "ProcessCustomerEventsWrapper" - System Reports Requestor Already Tracing

General
, ,
1

Hi Team,

I am trying to trace the Queue Processor ProcessCustomerEventsWrapper from Admin Studio. However, whenever I attempt to start tracing, I receive the following popup message:

“ProcessCustomerEventsWrapper is being traced currently by requestor: H9K0KY9MG53GOGEVK7CT2Z95BVK9X2NP8A. Please try after sometime.”

  1. The requestor ID displayed in the popup belongs to my own operator session.
  2. I verified the requestor in the Active Requestors landing page.
  3. The trace does not appear to be actively running from my side.
  4. Other team members are experiencing the exact same issue.
  5. For each user, the popup displays their own requestor ID as the requestor currently tracing the Queue Processor.
  6. This behavior persists even after refreshing the browser and starting a new session.

Expected Behavior

The queue processor trace should start successfully, or any stale trace lock should be automatically released.

Actual Behavior

The system continuously displays the message that the Queue Processor is already being traced by the same requestor, preventing trace initiation.

Questions

  1. Has anyone encountered this issue with Queue Processor tracing?

  2. Is there a known stale lock/requestor trace record that needs to be cleared?

  3. Are there any DSS settings, nodes, or background processes that can cause this behavior?

  4. Is there a recommended way to manually release the trace session for a Queue Processor? (note ; have tried terminate trace option. that also won’t help)

image
image1800×283 18 KB

2

Could you try terminating H9K0KY9MG53GOGEVK7CT2Z95BVK9X2NP8A from the Requestor Landing Page in Admin Studio and check?

3

Can you please share the pega version you are using?

4

Pega Infinity 24

5

I’ve tried terminating trace from requestor landing page. but it’s show below popup. i.e., this option also won’t help.

image
image894×291 7.01 KB