Script Debugger not Working

[aj78]

Hi,

While trying to debug the business rules script the script debugger is not responding.

I have placed the code in business rules > script pane. The condition is placed to trigger business rule is implemented 'after database Insert' on 'live_message'.

Since last successful update of Madrid. Debugger is not working properly. Breakpoints are not able to pause the flow of execution.

Kindly help.

Regards

aj

[Siva59]

Hi Chris,

     Facing the same issue unable to debug from project instance, is there any steps you followed to resolve this. If you share me it will be very helpful.

[howieoak]

We have the same problem after on-premise upgrade to New York. Script debugger is not working.

Personal dev instance with New York is OK.

[emyrold · Accepted solution]

I have a script include in a scoped app that I used to be able to step through in the debugger and now the Debugger just sits at Status: WAITING_FOR_FIRST_BREAKPOINT user: System Administrator.

I read in Doc's that it will work if isInteractive() is true

var interActive = gs.getSession().isInteractive();

gs.info(interActive);

When I run this in scripts background, it says false.  I know I used to be able to call this and step through, any suggestions or ideas?

Just created this test in a scoped app:

created basic script include and set accessible from "all application scopes"

name: test

script: 

function test() {
	return 'hello world';
}

// called from scripts backgroun in the same scope
gs.info(test());  // hello world

 launched script debugger from the script include, added break point and it never stops at breakpoint

[Chris L5]

So... is this question answered then ?

It sounds like there is a reproducible issue -- at least in terms of everyone's understanding (on this specific article).  

Or, has someone found a way to get the debugger to stop.. and I am just not realizing the significance ?

Follow Up Question --- maybe the core issue would be better understood.. if someone could point out a way to identify any internal errors that 'might' indicate WHY the Debugger is not stopping ?

Would there - perhaps - be some kind of Error Message that could yield insight into what the Debugger is experiencing when it won't stop at the break point ?

[Mike322]

I'm stuck on the same issue as OP and the accepted solution isn't really a solution as it's more of a deeper dive into what might cause the debugger to not run.

Is there an actual solution in how to resolve this issue? It's driving me nuts right about now.