Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×

API Library error: No existing sandbox found, restarting, endless loop (Hoard of the Dragon Queen v1.5)

I'm running a Hoard of the Dragon Queen campaign which I updated to the latest version (1.5) yesterday. We had terrible lag yesterday including several Red Boxes "You've been disconnected from our servers" messages. I thought it may be the APIs and when I  looked at the API output console, it kept repeating "Restarting sandbox by user request... No existing sandbox found.  Preparing sandbox to start on game activity.", so I disabled them all, then restarted them one by one. It reduced the lag dramatically, but not completely. This morning, when I checked, the API Output console is back to repeating this message: "No existing sandbox found.  Preparing sandbox to start on game activity. Restarting sandbox by user request..." I deleted all the API scripts, but no luck. I made a new copy of the campaign and the API screen says this: "Error downloading scripts (probably no scripts exist for campaign.)" If I add any script, I get the following message: "No existing sandbox found.  Preparing sandbox to start on game activity." How can I fix this?
1615642384

Edited 1615647015
ok, I deleted the api scripts, rolled the game back to yesterday. The sandbox said it was empty and ready to import scripts. I was able to import several with no issues. It looks like deleting, and rolling back resolved the issue, however I cant delete any tokens from the screen. edit: It worked for a little while, but I'm getting the same problem.
More debugging. The issue appears to be with the ApplyDamage.js script that I was using. If I dont add it to the campaign, all others work fine. This issue only appeared yesterday.