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 .
×
Create a free account

API Error

I've recently been getting the following error when I restart the sandbox. detected currently running sandbox... restarting "Loading character sheet data..." "Starting webworker script..." "Loading 755 translation strings to worker..." "Starting webworker script..." "Loading 755 translation strings to worker..." "SyntaxError: Unexpected token '.'" "SyntaxError: Unexpected token '.'     at eval (<anonymous>)     at messageHandler (evalmachine.<anonymous>:713:6)     at process.<anonymous> (/home/node/d20-api-server/node_modules/tiny-worker/lib/worker.js:65:55)     at process.emit (events.js:310:20)     at emit (internal/child_process.js:876:12)     at processTicksAndRejections (internal/process/task_queues.js:85:21)" I removed all the API scripts.  When I did that, i got an error about no scripts.  So I've loaded one script in.  Got the same error.  Removed the script, added a different one, got the same error.  It doesn't appear to be the API scripts.  I'm running the 5e OGL character sheet
1629574263

Edited 1629574278
I have the EXACT same error. I did the same things.
1629577456
Kraynic
Pro
Sheet Author
You might want to check the thread for the 5E character sheet in the character sheet forum.  That error might be specific to that sheet, since I'm not seeing any errors.  I don't run 5E, so that might be the common thread.
1629586143

Edited 1629586258
keithcurtis
Forum Champion
Marketplace Creator
API Scripter
I have seen it reported elsewhere. It sounds like a temporary glitch, and as long as it is not crashing your sandbox, can be ignored for now. Edit: Here is the thread , for anyone who wishes to follow the issue.
Yeah, it appears that the sandbox is still running in my case.