Debugging 429 Errors: Accessing Raw HTTP Responses with Helicone
Debugging 429 Errors: Accessing Raw HTTP Responses with Helicone
At a glance
The community member is experiencing a high number of 429 errors and is trying to debug the issue. They are asking how to see the raw HTTP response from Helicone. In the comments, another community member mentions that their provider was not automatically adding money to their account, which has now been fixed. They suggest that it would be helpful if Helicone could proactively provide this information in the response headers.
Ok for some reason my provider wasn't automatically adding money to my account, fixed now. It would be a-mazing if Helicone could proactively tell me that as I reckon you'd have enough info in the response headers
