[API] "API sandbox shutdown due to campaign inactivity." While working on Scripts and in-game.

Hey everyone - For those that are experiencing this problem, would you mind trying the following and letting me the results, please? Thanks! Have open only one instance of Roll20 and choose only one game to troubleshoot for now - close all other tabs/windows/instances/games Log out of Roll20 Clear browser cache Log back into Roll20 and go to the game having issues Now open up a second instance/tab/window of Roll20 and also go to the same game having issues In one instance open up the API Settings page and in the second instance launch the game When the game has launched, restart the API Sandbox in the API Settings page Check the API

Styrud said: It didn't work. I've tried it trice but to no avail :C Hi Styrud - Thank you for confirming that. I have reported this to our development team and they will investigate as soon as possible. In the meantime, to clarify, are you still receiving the same message in your API Console of "API sandbox shutdown due to campaign inactivity."?

Moving report here:  ENDSVILLE  said: Judging by a couple of other forum posts, something is wonky with the API these days... I was working on some macros which relied on one or more scripts in my game, and they suddenly stopped working. I checked the API page for that game, and it's stuck on repeat with the following message: Restarting sandbox due to script changes... I hadn't made any manual changes to any of the scripts for days, and everything was working fine until... well, until it wasn't. I tried looking through the one-click scripts to see if any updates may have happened, but I honestly couldn't be bothered to look through all of them >.> I also tried disabling several scripts to see if anything changed, but the sandbox doesn't even seem to get to the point of trying to load the scripts, so it - perhaps predictably - didn't help. A test game I had lying around works just fine. I was also able to make a copy of the affected game without any problems, and so far it seems to be working if I re-add scripts to the copy. In this particular case, I'll have to do some repeat setup work and assign some graphics again, and if I end up using the copy I'll try to see it as an opportunity to get rid of some clutter, as I have been testing a few things and realized I don't really need/want all the scripts I originally had, but I figured I'd report this anyway since it came somewhat out of the blue and had me freaking out a bit. Cheers.

Moving report here:  Dave T  said: Same issue here. Haven't tried another game, however. EDIT:  Confirmed that API works on other games.

Hey everyone - We've gone in and reset the API servers so everything should be functioning smoothly now and this issue should be resolved. Please let us know if you continue to experience any problems. Our sincerest apologies for the disruption to your gaming!

Dresdon said: So I tried cloning my game to see if that would fix this error. Well the script API now starts, so I started adding in the scripts I use, then I get this: 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:  TypeError: Cannot read property 'N' of undefined TypeError: Cannot read property 'N' of undefined at apiscript.js:11:16 at eval (eval at <anonymous> (/home/node/d20-api-server/api.js:154:1), <anonymous>:65:16) at Object.publish (eval at <anonymous> (/home/node/d20-api-server/api.js:154:1), <anonymous>:70:8) at checkForReady (/home/node/d20-api-server/api.js:1441:12) at /home/node/d20-api-server/api.js:1521:9 at c (/home/node/d20-api-server/node_modules/firebase/lib/firebase-node.js:14:64) at /home/node/d20-api-server/node_modules/firebase/lib/firebase-node.js:93:560 at hc (/home/node/d20-api-server/node_modules/firebase/lib/firebase-node.js:39:147) at Kd (/home/node/d20-api-server/node_modules/firebase/lib/firebase-node.js:93:546) at Id.Mb (/home/node/d20-api-server/node_modules/firebase/lib/firebase-node.js:93:489) at Zd.Ld.Mb (/home/node/d20-api-server/node_modules/firebase/lib/firebase-node.js:94:425) at /home/node/d20-api-server/node_modules/firebase/lib/firebase-node.js:111:400 However that stack trace doesn't look to be sourced from any of the scripts I have but something in the back end. Hi Dresdon - What scripts are you using in your game? Can you try to disable and re-add them one by one to see if a particular script is causing this error?

Dresdon said: I had running: DLEllipseDrawer, Torch, Page FX, TokenMod, CombatTracker from the Roll20 Script library. 5eTreasure and BlindRoll as custom scripts. I disabled everything and then turned them back on one by one, It looks like DLEllipseDrawer is the one at fault - Version was 'Latest' Hi Dresdon -  I experience the same issue as well when I install that particular script. I'll go ahead and let our API team know that script is having some troubles and we'll see if we can get in contact with the creator. Thank you!

Dresdon said: I had running: DLEllipseDrawer, Torch, Page FX, TokenMod, CombatTracker from the Roll20 Script library. 5eTreasure and BlindRoll as custom scripts. I disabled everything and then turned them back on one by one, It looks like DLEllipseDrawer is the one at fault - Version was 'Latest' Hi Dresdon - We are following up with the creator to get this resolved as soon as we can. In the meantime, as a workaround, would you mind trying to go to the tab for the script (DLEllipseDrawer), edit the value  N  under  User Customization Options  to anything else (e.g. 21), and hit save. After you have saved, go back and re-edit that same value to 20 and re-save again. After that, the script should work.

PapaWhiskey11 said: It looks like this might be occurring again. Hi PapaWhiskey11 -  Could you further describe what issues you are experiencing, please? Is your API Console displaying a particular error per chance?

Dark Galaxies Gaming said: “API sandbox shutdown due to campaign inactivity." wont let me restart scripts Hi Dark Galaxies Gaming -   To best help us with troubleshooting that issue, would you mind trying the following steps first and letting me know the results, please? Thank you! Have open only one instance of Roll20 and choose only one game to troubleshoot for now - close all other tabs/windows/instances/games Log out of Roll20 Clear browser cache Log back into Roll20 and go to the game having issues Now open up a second instance/tab/window of Roll20 and also go to the same game having issues In one instance open up the API Settings page and in the second instance launch the game When the game has launched, restart the API Sandbox in the API Settings page Check the API

Hi Michael -  Thank you for providing that information and our sincerest apologies on the delay! For this, would you mind trying to create a full copy of the game in question, re-installing one of your scripts, testing it again, and letting me know the results, please?

Hey Michael -  Yay! Glad to hear it worked! However, if you have any other troubles with your scripts, or if there is anything else that comes up, please don't hesitate to let us know. Happy adventures! :)

Hey all - Thank you for the reports. I have DevOps taking a look at this right now - we'll try to get you back to gaming as normal as quickly as we can. We appreciate your patience!

Hey everyone -  For better report consolidation, please refer to and utilize this post for further communication regarding this issue . As a result, I'm going to go ahead and close this post. We appreciate your patience!