DXWarlock said: I don't believe so. I wanted this (and actual script/line number errors that make sense to help with finding that error, since the scripts are all concat into one big one when ran..making line numbers in errors useless). The best you can do I believe, is what some of The Aarons scripts, and the Pathfinder sheet comp sheet does (and maybe others, they are just the ones I've seen) where you use a catch() in the script to grab the error and send it to chat to let you know, before it can actually crash the sandbox . But once the sandbox is down, you would be in a catch22. No sandbox running for the button you created to run in, to restart it. Sort of like having a man that just passed out, slap himself to wake himself up :) I believe the only true solution to achieve what you want is a suggestion post asking for that to be added to Roll20 itself. Unless some of the way more advanced JS gurus here know a way to do it scriptwise. Ok - so what I see there is what I mean. In other words, you have an API that all it is is a listener for errors. If it finds one, it quickly compiles an output to send to chat but also includes a link to the macro its made in the global macros list, that can restart the API sandbox without using an API to do it (not sure if a macro can do that with GM/ Pro subscriber level auth though - thats something that probably only an API could do). Even a spit out of error would be useful to know immediately that there was an error, to help in tracking down its cause.