Why does Try / Catch in Google Apps Script stop code execution in debug mode?

Question

I am using Google Apps Script in a Google Sheet. I added some code recently that was causing an error due to me trying to access locked data. I tried some basic error trapping using Try / Catch and this works fine when I run my code, but in debug mode the program halts execution on the line in question. Am I using Try / Catch wrong, or is there something else I'm missing?

Here's my code:

  for (var i=0;i<userGroups.length;i++) {
    try {
      var temp = userGroups[i].getUsers();
    } catch(error) {
      console.log(error); 
    }
    ...

NOTE: I am NOT using the V8 runtime as it was causing me a lot of issues.

Please add a minimal reproducible example including what runtime time are you using (old or Chrome V8). — Wicket
– Wicket, Commented May 25, 2020 at 19:09
Did you implement a breakpoint? The debugger is meant to stop at breakpoints. — ziganotschka
– ziganotschka, Commented May 26, 2020 at 10:50
I've done a number of experiments tonight and the ONLY time I am able to replicate the problem in my post is when I get the error: You do not have permission to view the member list for the group: [email protected] (line 265, file "Code") I can use Try / Catch to trap this error and that works fine when I run my code normally. But when I use debug mode my code breaks on getUsers() (the line in question). — John Cutter
– John Cutter, Commented May 26, 2020 at 18:55
(I tried to edit my post above, but I waited too long.) To be clear, I don't see this issue with any other errors I tried. It only seems to happen with permissions. — John Cutter
– John Cutter, Commented May 26, 2020 at 19:27

ziganotschka · Accepted Answer · 2020-05-27 10:12:38Z

2

If you are not using V8, it is an intended behavior that the debugger stops execution at any error - handled or not

Indeed, some users even complain about the fact that in V8 this feature has not been maintained.
If you on the flipside are happy with the debugger not stopping execution at handled errors - change to V8.

answered May 27, 2020 at 10:12

ziganotschka

26.9k2 gold badges18 silver badges34 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

John Cutter Over a year ago

I was just coming back to post this. An engineer at work wasn't able to reproduce my problem using v8. When he went back to the old version he saw what I was seeing. I'll give v8 another try.

Denny Ceccon Over a year ago

The debugger is pausing on V8 and I would really like to turn it off. :(

Monu Yadav Over a year ago

It's a stupid feature honestly. It ignores my breakpoint and rather goes on its own journey through a loop. No one can possibly sit through a loop iterating 100's of times and pressing continue each time.

Mr P · Accepted Answer · 2021-09-02 21:29:22Z

1

To work around the issue of the V8 debugger pausing on an error in a try catch, put the code with the try/catch in a library and call that code from your script by referencing the library. This way the try catch is occurring outside the debugger's control.

answered Sep 2, 2021 at 21:29

Mr P

611 silver badge4 bronze badges

Collectives™ on Stack Overflow

Why does Try / Catch in Google Apps Script stop code execution in debug mode?

2 Answers 2

If you are not using V8, it is an intended behavior that the debugger stops execution at any error - handled or not

3 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

If you are not using V8, it is an intended behavior that the debugger stops execution at any error - handled or not

3 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related