has anyone ever seen phantom debug statements in t...
# suitescript
k
has anyone ever seen phantom debug statements in the execution log before? I recognize the debug.log() statement as being in a very old version of the script - but it's definitely no longer there... and when I double check the current live version of the script via 'Edit', the log.debug statement isn't there... yet every single execution cycle it still prints the two phantom log.debug statements...
m
Does your script reference any custom modules? If so, any
log.debug()
statements in those modules will trigger in your script as well. Maybe that's where the logs are coming from?
s
if it's a client script there can be caching issues involved
k
nope, does not include any custom modules, and it's a scheduled script
it's bizarre
this log.debug statement would have been removed months ago
s
and of course for sanity you downloaded the script from the file cabinet to confirm it doesn't have that log statement?
k
downloaded from both the script record and the file cabinet (of course, they should be the same, but just in case...) - and no, no log statement
p
Download the entire SuiteScripts & SuiteBundles folders from the file cabinet as .zip files and then search them once you’ve extracted
Might be something you’ve forgotten about
k
the ghost statements haven't shown in the last two executions, so I'm going to guess it was something that I put straight into the script to debug and then forgot. Then due to the scheduled nature, maybe the updated version was lagging behind a few cycles. Mystery solved 👻
👾 1
(maybe)