{"code":"SCSX009","description":"Script launch interval time has not elapsed"}

[Maryna Brodina]

Hello Andrew!
Could you share your app with a href="mailto:support@appery.io" rel="nofollow"support@appery.io/a and tell us steps to reproduce?

[Andrew Peacock]

Hi Maryna,

It's already shared (I sent a support mail about the issue). Just open the app in the Test view, or in the Appery test app on your android, and you'll get a popup with the error on the initial page. But if you hit the refresh button on that page - which calls the same service - it works fine.

Regards,
Andy

[Maryna Brodina]

Thank you! Could you remind app name?

[Andrew Peacock]

PromoteYourCharity.

[Kateryna Grynko]

Hi Andrew,

Could you please also share your script?

[Andrew Peacock]

Done - sorry, I'd not realised the scripts had to be shared separately.

[Kateryna Grynko]

Hi Andrew,

Please try removing all codeconsole.log()/code from your code. It doesn't affect the results so you don't need it. This should speed up the code execution.

[Andrew Peacock]

Ah, thanks Katya! Removing the console.log() statements has resolved the specific problem I was having on page load

So... back to the original question I raised - I'd still like an answer on whether the original 300ms rule applies, or whether this has been removed.

I can't find anything about any burst limits on the pricing pages, or the appery.io terms and conditions page.

Regards,
Andy

[Illya Stepanov]

Hi Andrew,

We will update our pricing page soon. So, on your question:

Restriction : script burst rate (launch interval):
ul
liStarter : 300 ms;/li
liStandard : 125 ms;/li
liPro : 100 ms;/li
liPremium : 50 ms;/li
/ul

[bahar.wadia]

In other words, server side scripting is not useful for any scalable application. Better just for testing and limited use case scenarios.