400 Super Scaling Error

Application ID: AE4235E1-DBB7-C6F0-FF4A-E0378B0B2B00

Problem description

Describe what you did in console that led to the error. Please provide a description of what actually happens. Be descriptive: “it doesn’t work” does not describe what the behavior actually is. This will help us with reproducing the problem.

Steps to reproduce

Please describe steps to reproduce starting from the first action.

  1. Try to invoke the awsAPIs sendSESEmail service

I get this error when I try to invoke an API service:

400 - 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. (9070)

What is causing this? The logs don’t give any indication as to what the API service is doing to exceed some quota.

The application is on the Springboard, which does not have the Superscaling feature. Apps on the Springboard plan have limited transactional capacity. The backend will handle requests from a limited number of unique devices (the list is refreshed daily) and can process only a limited number of concurrent requests.

Regards,
Mark

@mark-piller Is there any way to tell what the root cause is? I changed the API service to not use transactions, and I don’t get this issue with any other API services (so it shouldnt be my device), but I still see the same error. Would a very large API payload cause this? I am sending a body that includes an array of 1000 UUIDs.

Hi @Christopher_Manzi1

According to our logs, the reason for the issue was exceeding the allowed number of concurrent requests for your application on the Springboard plan.
The payload size is not the cause.

Regards,
Viktor