Unexpected token s

Has there been any progress on this issue? It causes me to have to restart the API about twice per session now. Is there any work around?

Are you saying that you are getting this crash while using the API?

Yup. <a href="https://app.roll20.net/forum/post/1647248/unexpected-token" rel="nofollow">https://app.roll20.net/forum/post/1647248/unexpected-token</a>

The Aaron said: Are you saying that you are getting this crash while using the API? It didn't happen to us last night, but most nights it'll happen once or twice. It also always happens when the campaign is 'shut down'.

I thought this was fixed, but it appears to be back this week with a vengance. I'm guaranteed to get it when starting up a new session after a break and it looks like I'm making my way through the alphabet. It used to always be "s" but I've seen "i" and others.

I've seen this error on one campaign that wasn't using any scripts... How could this be?

Vince said: I've seen this error on one campaign that wasn't using any scripts... How could this be? Odd. Me too. I just checked one of my campaigns with no scripts (never had any) and it has the 'unexpected token s'.

This crashes my api...when no one is ever logged into the campaign. I've been trying to track down what might be causing it, but so far I havent been able to narrow it down.

FYI - Still happening 2 weeks later. I was running 3 scripts, then started getting the error. I deleted them all before I learned about this issue, but the error continues with no scripts installed.

I have 2 test campaigns this is happening to currently. The first has 20 scripts, 13 active and is reporting 'Unexpected token s' The other has only 3 scripts, all active and is reporting 'Unexpected token {' 2 of the 3 scripts in the second campaign are identical to scripts in the first, and the 3rd has 2 single character diffs. Neither is a 's', or a '{'... Is there a way we can get the error message to include the entire statement the interpreter is trying to interpret.

Still happening for me as well. Before it was only some times, now it seems to be every time the sandbox shuts down and restarts due to inactivity.

Also having the 's' error. I went from 1 to 4 scripts and have the impression its more frequent now, and seems related to when the previous sandbox shuts down on its own, like Joshua V says. I scanned the active scripts for missing semi-colons but there are so many other possibilities...

Any progress on this issue?

Part of the changes rolled out yesterday are better tracking for this issue. &nbsp;After the dust settles, hopefully the devs will get some better debugging logs to be able to track it down.

Awesome, thanks for the update.

Looks like there is less information now. I opened the API editor and it says: 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's no longer an unexpected token error, it's just blank now. When I hit save script, it saves and everything works great until the next time.

Less information for you, but more logging for the devs. &nbsp;I noticed that as well.

I feel better knowing it's no longer just me.

It has been months since this problem surfaced. Now I'm a patient person but ... 5 months? This breaks most campaigns that rely on this feature.

Is there anything us users can do to help solve this bug?

Not really, so far as I know.