Occassional dead script

[nikkujensen]

Hi @jamesjonesmath

First off, this script is excellent. It has saved me much time when I have needed to create complex rubrics. Thank you!

However, as with most technology I use, it is great until it doesn't work... 😏

Recently, I have experienced this script just go dead for a bit. It only happens occassionaly and I am not sure what it could be due to because there is no error kicked out. Recently, I tried importing this rubric. After trying to use the script a few times, I removed tampermonkey, let it sit for a day, and reinstalled it. After this, things worked just fine.

I am wondering if there are any best practices I am missing or if there is an issue with the script. Please let me know.

Sincerely,

Nick
HW7-Rubric.xlsx

[jamesjonesmath]

Intermittent problems are the worst to track down. I just imported what you attached without any problems using Tampermonkey in Chrome on a Windows system.

It might have been a problem with Tampermonkey, the author does make releases periodically and their was one in the last few days. When it upgrades, it comes up with a notice that you will have to reload any running scripts, but I took that to mean that if you already had a page open then it would need reloaded. Unless you live on the rubric import page, it shouldn't be a problem.

As far as debugging, you can try to open the browser's developer tools and look at the console and the network tabs. I don't log a lot to the console, but if there was ever an error (not just a warning), it would prevent the script from running and it would show up there. For the network tab, look to see if it is making the call to Canvas and if so if there is any error associated with that. If it never gets that far, then we know to look at the code before it saves the rubric.

Another thing I do during debugging is kind of old school, but I go through and put console.log('message'); statements at the top of functions. The 'message' is usually the name of the function. That way I can tell how far the code is getting before it times out. Be sure to save the script and reload the page when this happens. Once I find out which function that should be called isn't being called, I go to the function before it and start adding console.log() statements to key points there.

Chrome has the ability to add breakpoints to the actual code and that would be a newer school method of debugging.