Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Failed deployments due to throttling

See original GitHub issue

I’ve been getting intermittent failed deployments, apparently due to the API requests being throttled. The output is:

Created new application version d00348b in Beanstalk.
Starting deployment of version d00348b to environment ***
Deployment started...

03:05:18 INFO: Environment update is starting.
##[error]Deployment failed: Error: Status: 400. Code: Throttling, Message: Rate exceeded
##[error]Node run failed with exit code 2

Has anybody else come across this issue or have any suggestions on how to rectify it?

Sometimes occurs even when doing the first deployment of the day.

Issue Analytics

State:
Created 4 years ago
Comments:21 (11 by maintainers)

Top GitHub Comments

1reaction

einaregilssoncommented, Mar 18, 2020

Published v8 which has the throttletest branch merged in. Don’t log it as a warning anymore when getting a throttled requests, just log it normally. Closing this issue now, will re-open if there are more problems.

1reaction

einaregilssoncommented, Mar 13, 2020

@kceb That’s actually a great idea, and what I probably should have been doing from the start. I’ve uploaded a special branch to try it out, can you try using

uses: einaregilsson/beanstalk-deploy@throttletest

in your deployment script and see whether that works for you? It will allow up to 5 consecutive requests to fail with a throttle error before failing the deployment, and will log a warning if it gets a throttle error. If it does work, please let me see the logs to get an idea of how many times the requests were throttled.