Pause "On Unhandled Exceptions" stopped working (Intuitive Debugger)

[rogeriodec_games]

Reproduction Steps

1) Set in scripts to pause “On Unhandled Exceptions” (if not already set) and close Studio:

2. Open Studio and create a LocalScript
3. Put this to force an error:

a = {}
print(a.b+1)

4. Run
   
   

Expected Behavior

The debugger should stop at the error line

Actual Behavior

The debugger does not stop at the error line. This started to happen after this:

"old" debugger disappeared

Reproduction Steps I never liked the Intuitive Debugger: Slow, bureaucratic, clumsy, difficult to use. But apparently Roblox is imposing this new version, as I can’t find it anymore to disable it in Beta features. Expected Behavior I want the old debugger back. Actual Behavior There’s no option to deactivate Intuitive Debugger anymore. Issue Area: Studio Issue Type: Other Impact: High Frequency: Constantly Date First Experienced: 2023-01-23 00:01:00 (-03:00)

Workaround

Manually select “On All Exceptions” and then click “On Unhandled Exception” again.

• But if I close Studio and open it again and repeat the process, the problem reoccurs.
  

Issue Area: Studio
Issue Type: Other
Impact: Moderate
Frequency: Constantly
Date First Experienced: 2023-01-23 00:01:00 (-03:00)

[rogeriodec_games]

As I reported here (ABSURDLY SLOW DEBUG (Intuitive Debugger) - #4 by rogeriodec_games), Roblox has again allowed to disable the Intuitive Debugger.
But the problem reported in this thread remains, so I’ll keep it open.

[KapokPanda]

I am experiencing this as well. To add context to the level of impact:

We rely on this debugger break to catch problems during development. If they get silently buried in output spew, we miss critical problems during regression tests. Please fix this ASAP.

[thirdtakeonit]

Thanks for the report! We’ll follow up when we have an update for you.

[altisaltaccount]

Hello folks! There was an issue with initialization for that setting, which is why switching between settings made it work again, but restarting the Studio would re-surface the problem. This issue should be fixed now.

Cheers!

[rogeriodec_games]

Testing the same situation (after activating Intuitive Debugger), it seems the bug was solved.
Thanks.