This happened on 2025-08-25 which was day 1 en6c email send and second week of sending volume through gravy paypal

@AMJohnson noticed that we were getting failures in the gravy console with no error messages and when digging into them further they had an error on the vault api with 429
service_rate_limit

example gravy id 0829fa34-a7f4-46a7-aaba-625776700ebf

Gravy got in contact with paypal and upped our rate limit but the traffic had trailed off too in the meantime

Response from paypal
"When looking at our logs for your Client ID, I am seeing a spike in the 429 errors between 0900-1000 Pacific today. The errors have stopped after that, and we are now seeing normal processing results on your Client ID. If you recently went live, it may have inadvertently triggered a rate limiter on our end, but since our rate limiter dynamically flexes with traffic, it may have auto-corrected."

This happened again on 2025-09-04, two donors emailed about it. I have sent PayPal an email asking if our limit can be increased as we don't have consistent traffic