can anyone else not access Debugger in SB accounts?

@Chris Deakin is also not able to do so

I tried and it took me back to the "click here to log in to the debugger" screen which I did and then it worked.

it keeps taking me to the click here to log in even though I'm using debugger URL

I logged in through the regular login then chose to login to the debugger through customisation....

yep tried that way too - nvm I'll wait a little to see if it comes back. Thanks

I'm in a meeting but will ask my colleague who had the same issue previously if it was resolved for him when I'm out of it

y'all must write some complex code - I don't find myself wanting for a debugger with suitescripts.

I have only used the debugger when @NElliott said it was a good idea. lol

@stalbert I tend to use the debugger to knock out code snippets and see if what I think happens in NS actually happens 😉

debugger is back.... hooooraaayyy

@SimonC you're welcome (psss, /whisper what did I do to help?? 🙂 )

you brought us luck

I may sound contrarian, but it sounds like i've used local unit tests instead of the debugger when code gets complex. I've used the NS debugger maybe 4 times in a decade. If NS came out with a high performance remote debugging experience I'd reconsider. But for many years I've been crafting good suitescript code without the debugger and I don't feel I'm missing out. Then again, I leverage libraries and patterns that make the code I'm writing fairly simple and concise.

I use the debugger for when the output of my code is different on the netsuite server than on my computer or in the browser

The problem with the sandbox only occurs in certain accounts, I have a case opened with NetSuite at the moment.

Yeah only the people who pay for it.

It appears to be a defect and is a U4 which means it will be fixed in the next 3 weeks!!!! "Case # 3287738 Update: "Defect 524205: Debugger Stopped Working"

Busted in a TSTDRV account