We have stood up a Service-REST in our application. An upstream app will send an update request for which we open the case and make some updates. Recently, there were some delays reported and while debugging, we found the service requestor id is in "Traced" status in the Requestor management page in Admin Studio. Then when we terminate that trace session, the processing is completing quickly. It’s a basic auth requestor operator id which is not used by any app users, so we don’t know how the request is going to "Traced" status (see screenshot) and getting stuck.
Can someone please let us know how/why these requestors are being automatically traced when the requests are received and how to stop it?
***Edited by Moderator Marissa to update Content Type from Discussion to Question; update Platform Capability tags***