I am trying to debug a SS2.1 script, but I am getting the Websocket disconnected error everytime, anyone else is experiencing this?

@Toni Capella I'm getting the exact same thing. I'm in a dev account - are you in a standard account, please?

Yes it happens in several acccounts to us. Dev, Sandbox and Production

I just assumed this was the expected behavior when a script in the debugger ends.

Well, it's 17:24 where I am and so far I've had a support ticket fail to submit and the debugger is broken, so I think NetSuite's irony department must be on double-time, and it's time for me to call it a day. Hopefully it's resolved by tomorrow, if not I might raise a ticket ... wait ...

ouch! Yep. I'm seeing the same thing.

Ah well, time for some food, some guitar n some sleep, and maybe NS will have sorted its head out by the morning. Thanks for the confirmation Mike, 3 strikes n it's a bug 🙂

I never use the web debugger.

Good morning, is this still happening to you guys?

@Toni Capella It was still happening for me around an hour ago. Alternative for me is to use chrome dev console, but that's problematic if I need server side stuff.

Exactly, I need it for serverside testing

I wonder if the 'standard' debugger is working, I can't remember if 2.0 runs in console or NetSuite original debugger.

Yes, 2.0 is working as it is using the old debugger style. To adapt to 2.0 is not an option at the moment for us

I haven’t been able to use the debugger for the past two days.

The scripts I write tend to be clear and concise (due in part to the libraries and practices) and do unit tests if things are more complex (i.e. tests that run locally to test business logic). So long story short, I rarely needed more than a few execution logs for debugging when code is finally running in netsuite. I also always felt the debugger was rather slow and klunky compared to other source level debuggers on other platforms, so that was a bit of a turnoff.

@Shawn Talbert That all sounds like good practice, but it sounds like you're disparaging use of the debugger. It's a tool provided for a purpose, and there's really no reason it can't/shouldn't be used. In 2.1 it's a very useful tool as it opens in chrome dev tools, which is a lot nicer to use.

Whatever makes you most effective as a developer is fine with me.

@Shawn Talbert So, coffee then 🙂

That's a given 🙂

Anyhow, I've raised a case. It would help if others who want to use it also raise a case, otherwise they might just think I'm using internet explorer and wearing a tinfoil hat

Edge is the new Chrome

I actually like Edge. Internet Explorer was only good because it fell apart on any issue. In a way, Chromium based are almost too forgiving

True, though I wonder if having the vast majority of browser users on the same core (chromium) is the best thing

@Toni Capella They've essentially agreed there's a bug

Hello @Paul Lawton, yes I received the same. Thanks for sharing 👍

@Toni Capella No worries and thanks 🙂

it is now back up and debugging. happy debugging!!

Thanks @Patrick A. I hopped in to say NS had sent an update that it was resolved, but I haven't checked it myself yet - appreciate the heads up