function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
pluviosilla.ax1797pluviosilla.ax1797 

Suddenly I can't monitor myself in the Debug Log!!!

Very strange. I'm developing a trigger that sends me an email, and I have been debugging it by monitoring myself in the Debug. Now (this is really weird), suddenly, after running my trigger and deleting the accumulated logs, I am no longer able to monitor myself!! I am able to add any other user in the system, except myself.

 

Could I have hit some kind of limit?

 

Best Answer chosen by Admin (Salesforce Developers) 
TheDoctorTheDoctor

Are you able to see your logs in the Developer Console?

All Answers

kevin lamkevin lam

Have you tried resetting your log request?
pluviosilla.ax1797pluviosilla.ax1797

I can't reset it because, inexplicably, I can no longer monitor myself *at* *all*. I can monitor other users, but not myself.

 

In other words:

* Under "Monitored Users" I choose the "New" button.

* I get the usual dialog "Add Users To Debug Logs"

* I click on the magnifying glass, and select myself (as I have done many times in the past)

* I click on the Save button

* The dialog goes away, BUT I'M NOT IN THE LIST OF MONITORED USERS

 

I can monitor any other user in the system. No problem. Just not myself.

 

This is extremely bizaare. Again, this happened while I was testing an Apex trigger immediately after I deleted some accumulated logs.

 

Extremely bizaare.

 
TheDoctorTheDoctor

Are you able to see your logs in the Developer Console?

This was selected as the best answer
pluviosilla.ax1797pluviosilla.ax1797

Apparently not! When I try to open the Developer Console, I get this error:

 

Failed to load data Log from Salesforce.com: (id=07LZ000000CSpPa)

 

O.k., very interesting. After opening the developer console, I was able to go back and monitor myself. I know that was what fixed things because:

* Immediately before opening the Developer Console, I tried and failed to monitor myself in the Debug Log

* Immediately after opening the Developer Console, I tried and succeeded to monitor myself

 

TheDoctor, do you have any idea why that might have cleared things up?

 

 
TheDoctorTheDoctor

No idea. Glad it helped though.
Thomas DvornikThomas Dvornik
That page is now using TraceFlags to set monitored users. There is a known regression where if the trace flag for the monitored user expires, then you can't add that same user at a later date. One workaround is to delete the trace flag first. We are working on a fix.

I'm surprised opening the developer console fixes the issue. If it doesn't for anyone, you can also delete the trace flags through workbench or the Tooling API directly.
Sanchit SinghalSanchit Singhal
Thanks, deleting the user trace flags and recreating them worked for us!