Forum | Appery.io

Limits will be updated based on the plan. It's not possible to eliminate the limits, no service can do that.

I believe that I am under the same scenario as bahar, above. The nature of my app requires that users "check in" with the server for updates every 5 seconds. I'm using entirely appery products (app, server code, database) without recourse to anything 3rd-party. When multiple users are using the app, they sometimes get rebuffed by the server--often enough to be noticeable--with the SCSX009 error described above in this GetSatisfaction thread. At the moment, there aren't many users using the app, but I'm having difficulties thinking about how to scale the app from few-to-many.

I can often produce the SCSX009 error by pressing a "submit" button simultaneously on two separate apps.

Is there any particular type of architecture that you could suggest that would get around this scenario? Personally, I'm currently at a loss. Asynchronous communication? A queue? Some sort of a "thread" process that treats things like a service and works its way through the stack of tasks to do? I would say that I'm in the lower-intermediate level of ability and am open to any ideas.

We will be introducing a script execution limits. You will have an option to get a plan with smaller execution interval/limits.

Hi,
Has there been any progress on this (the 300ms rule)? I can't find anything about any burst limits on the pricing pages, or the appery.io terms and conditions page.

Regards,
Andy

Hello!

I'll check and let you know.

Thanks Maryna,
Andy

Hi Maryna,

I guess not. In testing, I'm getting "{"code":"SCSX050","description":"Script launch interval time has not elapsed"}" to a server script based service which is triggered on page load, when I refresh the page within a few second of the page finishing loading.

I've already shared this project with support - feel free to have a look.

Regards,
Andy

Hm. That's strange. I've just added a button which I can press to manually re-invoke the service, and now it's working fine. I'll keep an eye on it and let you know if I encounter further problems.

Ah, got it analysed. If I view the app in the test mode in the browser, I get the error when I refresh the page (via browser refresh), but it works OK if I refresh via the refresh button I added to the app, and it works OK if I hit the refresh button that is in the top frame of the test mode page.

Hope that helps.
Andy

Hi Andy,

Thank you for the update! Will let you know when have more information.