Error downloading scripts (probably no scripts exist for campaign.)

Having a strange new problem today: Your scripts are currently disabled due to an error that was detected. Please make appropriate changes to your scripts and click the "Save Script" button and we'll attempt to start running them again. More info... For reference, the error message generated was: Error downloading scripts (probably no scripts exist for campaign.) This started at 1:30 pm today on my Falleron Setting campaign, I only have one API script (powercards) and it remains untouched from the past 7 months. It was working fine during that 7 months and through this morning, now it won't load at all. It appears to hang on "Spinning up new sandbox" upon hitting "Save" to reset. Trying to enable/disable gets the error message above. My game session is set for tonight at 6:30pm, so any haste possible in looking into this is appreciated!

To follow up with this, one in 20 attempts to save causes it to fix, but it will then break at random later on. It is back up at the moment, but has done this two or three times since 1:30. Getting the responses of the powercards upon use is very sluggish (minute+ delay between macro click and display). Any suggestions on how to fix (or when the issue might be resolved) would be greatly appreciated!

When it crashes we get this error message: Your scripts are currently disabled due to an error that was detected. Please make appropriate changes to your scripts and click the "Save Script" button and we'll attempt to start running them again. More info... For reference, the error message generated was: There was an error communicating with the QuantumRoll server.

Not a unique problem to this campaign: <a href="https://app.roll20.net/forum/post/2995618/error-downloading-scripts-probably-no-scripts-exist-for-campaign-dot" rel="nofollow">https://app.roll20.net/forum/post/2995618/error-downloading-scripts-probably-no-scripts-exist-for-campaign-dot</a>

We are asking that all discussion relating to possible ongoing issues with the API be kept within our sticked thread in the API forum: API Issues (Feb 21) I've moved your posts over to the above thread, where we can better focus on troubleshooting. Thank you.