Hi everyone / Roll20 Support, I am running a campaign that plays bi-weekly. Recently, every time I launch the VTT, none of my Mod (API) scripts work, and I am greeted with the message: "API sandbox shutdown due to campaign inactivity." The Issue:
Previously, the sandbox would quietly boot up in the background whenever I or my players logged into the game session. Now, the automated wake-up trigger seems completely broken for my campaign. The sandbox remains permanently shut down until I manually go to the campaign's Mod Scripts settings page and click "Restart API Sandbox." Once manually restarted, the console outputs Ready with zero errors, and all scripts run completely fine during the session. However, as soon as the campaign sits idle for a few days, it returns to a hard-shutdown state and fails to wake up automatically on the next VTT launch. Details: Script Error Check: Console runs clean with no infinite loops, crashes, or red error logs upon restart. Subscription: Active Pro subscription. Impact: Having to manually navigate outside the VTT to hard-restart the sandbox every single time before/during a session creates unnecessary friction for our group. It seems like my campaign’s backend container or auto-wake listener is stuck or orphaned on an unhealthy node. Could support please take a look or recycle the server container assigned to my campaign? Campaign Link: <a href="https://app.roll20.net/campaigns/details/19647067/curse-of-strahd" rel="nofollow">https://app.roll20.net/campaigns/details/19647067/curse-of-strahd</a> Thanks!
