I am currently trying to develop my app using the springboard plan.
Ever since I tried the UI builder, I keep getting the following error : “The API request has been rejected because it requires scaling for processing. Switch to the Cloud9 or Cloud99 plan to enable the Super Scaling option.”
I imagined that the Stripe integration plugin could have triggered this traffic so I turned it off yesterday. However, after regaining access this evening I managed to load my page only twice before being blocked again. I tried it on two devices both connected to the same home wifi network, so it should be but a single IP address. App stats for today show only 38 total calls, 2 for data service and 36 for file service.
I admit that this is both quite puzzling and very limiting when trying to develop. Is there a way to “broaden” the filter, even slightly ?
The Springboard plan definitely allows for half a dozen devices. What I am not sure about is the Stripe callback. If it comes from different machines on their side, each would count as a separate machine and thus may trigger the SuperScaling alarm for Springboard.
I am creating an internal task to check all the locations where your app got hit from before it got blocked. Someone from the team will get back to you on this via this post.
Could you please repeat again actions which caused limit hit?
We store detailed information about used clients locations only for a day. Now from logs I can see only that your app reached “locations” limit.
Also one more question for clarification. You said that when you hit SuperScalling limit your app API was blocked completely. You meant that you was unable to access API from all devices from which you worked before during that day?
I left my project completely untoched for two days. And tonight as I try to resume working on it, I was able to perform only a few hits with the desktop preview, and two mobile simulators (on the same computer), and as soon as I tried the mobile preview, scanning the QR code, the API went back to error 9070.
As you can seen from the stats, this was really only very little work.
Also, as an answer to your additional question, what I mean when saying I reached the SuperScalling limit and the app API was blocked completely is that on all devices I have at hand (in my single location), they all return the same :
Honestly, I don’t understand how the Springboard is meant to allow for development. A few hits a day can’t allow for any productivity. That is unless you intend to nudge people to upgrade to the paid plan upfront rather that when they are ready for production. If that is the case, I would really appreciate if you were transparent about it. Please advise.
Thanks for the feedback. This could be a bug or you could be hitting it from a multitude of locations. I don’t know. However, if you believe there is an ulterior motive, and/or we are not being transparent, you are absolutely wrong.
We would love to figure this out and if there is a problem, fix it. By the time the engineering team is back, your app will be cleared and we will not know what led to the lock again. If you would like to help and try out whatever you did during standard business hours, it would be amazing.
Got it about the transparency and I appreciate your reply.
Therefore I will try to continue providing feedback to the team so we can get this solved. Trust me, I would love to, because as of today I don’t know how to test my app. Sorry if some of my frustration vented out.
I promise I have tried it only through my computer and my phone, having checked that both are on the same wifi network and with my VPN disconnected. From the outside, this should look like a single IP address.
In order to know what standard business hours we are talking about, could you tell me what time zone we are talking about ? I myself am working in Europe.
Thanks, Nicolas. Please try again tomorrow morning (your time) if you can. Report the issue if it happens and tag @Andriy_Konoz , he will be able to check the state of the app.
Did you use for access to the app your custom domain registered using CloudFlare?
I see a lot of accesses via their servers during the current day.
I think that it is main reason why your app was blocked so quickly - CloudFlare can use new proxy server for each request.
I would suggest you to use generated domain for development or do not use CloudFlare for your custom domain while your app in development.
Thank you for your reply and sorry for not coming back sooner.
Now that you mention it, this could be a good hypothesis. My domain is indeed served through Cloudflare, and I did have my custom domain set in the UI Builder > Settings > Published App’s API Key.
I suppose that is I revert to the standard domain, this should solve the issue. For good measure I also temporarily disabled the Cloudflare proxy.
Thanks a lot for looking into the issue. If ever it persists I will report back.
