Some operations (such as assigning a reserved IP address to a newly-created droplet) can return a 422 HTTP status code. According to the standards, 422 errors are not supposed to be fixable by retrying - but in these situations, they are.

The godo package automatically retries 429 and 500 responses, but not 422. Either the retry logic should be broadened to include 422, or the endpoints which return 422 for potentially transient reasons should be altered.