You need to sign in to do that
Don't have an account?

system log not working
This might be a dumb question, but for some reason I can't get the system log to return any information. I've got the window open set to Apex Code/Debug, and I know my triggers are executing because I've got field updates. But the system log remains silent, despite multiple System.debug calls. This worked just fine last week, no idea why it's not now. I made a couple minor edits to a trigger but that's it. I did purposely create an error and that came back in the UI fine, futher verifying that the trigger is firing and is calling my apex class. Field updates with my "debug" messages work and place the messages into the field, so it's definitely stepping through all the code.
I'm running Firefox 2.0.0.11 and Eclipse 3.3.1.1 with the latest Force.com IDE, on MacOSX 10.4.11. I just cleared out the cache, reloaded and still nothing. There's probably a really easy answer here, but what is it?
Mark
I'm running Firefox 2.0.0.11 and Eclipse 3.3.1.1 with the latest Force.com IDE, on MacOSX 10.4.11. I just cleared out the cache, reloaded and still nothing. There's probably a really easy answer here, but what is it?
Mark
i look to the debug log monitoring that is built into the app.
it's here:
https://na5.salesforce.com/p/setup/layout/ApexDebugLogEdit?setupid=ApexDebugLogs
also works great for debugging incoming email to apex classes
you may have to modify the "na5" to match your server
this log never fails.
Mark
i find that i have to restart my powerbook every few months, or when i see this type of thing happen, your mileage may vary.
Also, i use Safari as my favorite browser now, and go back to Firefox when i need to use firebug.
As soon as I recover a crashed Parallels hdd file (it's been a really good week), I'm going to try the system log there. If nothing else that will allow easy debugging while running Eclipse on a different screen. It wouldn't bother me so much if it hadn't been working perfectly just last week.
Mark
my catch statements call a class that sends an outbound email to me if an exception is caught. this saves me literraly hours of trudging through the web interface and making sure logging didn't magically turn itself off.
one thing that would be nice is if there were a way to programmatically access the same line by line data the log has, rather than just the error message, but beggars can't be choosers i guess.
I was going to try to use Firebug to find the source of the problem, but this kinda killed that idea. Maybe the two problems are connected somehow? It's been a bad few days....
Mark
Mark
I also tried other logins with the same problem, on both Windows and Mac OS.. Then I disabled Windows firewall and the Mac firewall and still no change. I finally verified with our IT department that no changes have been made to the company firewall either.
Completely frustrated at this point.
Mark
- Login to sandbox org.
- Open opportunity line item record in detail mode.
- Open System Log in a separate window and set to Debug mode.
- Use in-line editing to change the value on one custom numeric field.
- Click save.
- Watch the system log for the results.
This used to get an immediate response in the system log with a full log of the trigger run. Now, nothing.Update: This appears to be related to inline editing. I just tried it in full Edit mode and the log worked! FWIW it worked fine with inline editing last week. Hey at least that gets me working again!
Did something change in inline editing recently?
Mark
i don't personally use in-line editing as the page refresh still has to happen and you have to manually save it when you're done anyways. it doesn't really reduce clicks or time waiting for pages to load.
I still think the first release of the system log was the best. It gave nice clean, relevant info for debugging.
Message Edited by TehNrd on 03-17-2008 01:37 PM
Thanks,
Arnt
Mark