# Unable to Trace File Listener Activity

**URL:** <https://forums.pega.com/t/unable-to-trace-file-listener-activity/3860>\
**Category:** General\
**Tags:** updates, admin-studio, pega-cloud, java-and-activities, 8-8, system-administration, security, senior-system-architect\
**Created:** [January 27, 2023, 2:33pm UTC](https://forums.pega.com/t/unable-to-trace-file-listener-activity/3860 "2023-01-27T14:33:09Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![JorgeS62](https://avatars.discourse-cdn.com/v4/letter/j/e99b99/32.png) [@JorgeS62](https://forums.pega.com/u/JorgeS62)\
**Post date:** [January 27, 2023, 2:33pm UTC](https://forums.pega.com/t/unable-to-trace-file-listener-activity/3860/1 "2023-01-27T14:33:09Z")

</div>

Hello,

I am unable to trace the execution of a File Listener. Here are some relevant details:

- I am tracing the listener from Admin Studio

- Tracing Service in Cluster does not display anything, even after the file listener has been triggered and finishes execution.

- As seen in the screenshot attached…Tracing Service on Node **does** return **some** details but it does not display the steps of the activity executed by the Service File rule

- We have recently migrated from an On-Premise environment to the Cloud.

- I know that the activity is executing due to the fact that I can see parameters in the MyServicePage after the file listener has finished executing. (see screenshot)

Has anyone seen this issue before, or know what is causing the file listener to not show the activity steps being executed?

Thanks for your help.

Screenshot below:

 ![Tracer Screenshot.png](https://pega1.discourse-cdn.com/pega/original/2X/8/89d4eb100c223b15c378e0dc11845c5db60e5f8a.png)

 ![Tracer Screenshot.png](https://pega1.discourse-cdn.com/pega/original/2X/8/89d4eb100c223b15c378e0dc11845c5db60e5f8a.png)

---

<div class="post-metadata">

**Author:** ![CarissaW\_GCS](https://avatars.discourse-cdn.com/v4/letter/c/f14d63/32.png) [@CarissaW\_GCS](https://forums.pega.com/u/CarissaW_GCS)\
**Post date:** [February 1, 2023, 2:06pm UTC](https://forums.pega.com/t/unable-to-trace-file-listener-activity/3860/2 "2023-02-01T14:06:21Z")

</div>

Hi @JorgeS62

I was able to reproduce this issue on my system. Our engineering team is reviewing the behavior. I’ll let you know what we find out.

---

<div class="post-metadata">

**Author:** ![AAV7601](https://avatars.discourse-cdn.com/v4/letter/a/d2c977/32.png) [@AAV7601](https://forums.pega.com/u/AAV7601)\
**Post date:** [February 17, 2023, 7:59am UTC](https://forums.pega.com/t/unable-to-trace-file-listener-activity/3860/3 "2023-02-17T07:59:25Z")

</div>

@JorgeS62 @CarissaW_GCS

Any update on this, I am also facing this issue.

Thanks

---

<div class="post-metadata">

**Author:** ![CarissaW\_GCS](https://avatars.discourse-cdn.com/v4/letter/c/f14d63/32.png) [@CarissaW\_GCS](https://forums.pega.com/u/CarissaW_GCS)\
**Post date:** [March 20, 2023, 11:22am UTC](https://forums.pega.com/t/unable-to-trace-file-listener-activity/3860/4 "2023-03-20T11:22:13Z")

</div>

Hi @AAV7601,

A fix for the issue is targeted for the 8.8.3 patch release.

---

<div class="post-metadata">

**Author:** ![AAV7601](https://avatars.discourse-cdn.com/v4/letter/a/d2c977/32.png) [@AAV7601](https://forums.pega.com/u/AAV7601)\
**Post date:** [March 21, 2023, 11:11am UTC](https://forums.pega.com/t/unable-to-trace-file-listener-activity/3860/5 "2023-03-21T11:11:07Z")

</div>

@CarissaW_GCS

Thank you so much