Getting "Failed to parse Resend API response. Please try again." error

[miguel-arrf]

Hi!

I've been using Resend for the last 6 months, and it has been working very well (quite a pleasant experience)!

Occasionally I get a 'Failed to parse Resend API response. Please try again.'.

Does anyone know what might be causing these errors? Can it be because of rate-limiting? I want to fix these, and I want to retry when I get an error like this, however, without knowing the potential cause (like rate-limits) I can't be as precise as I would like for the fix!

Thank you!

(I was using version 2.5.1, I've now bumped it to 2.10.0, however, looking at the changelogs, I don't believe it will fix these or give me any more detail about the cause)

[miguel-arrf]

Ah, sorry, just one more thing!

Very very rarely, I get a 422 where the error is also 'Failed to parse Resend API response. Please try again.'. I know it is a 422 because if I check the logs page I can see it there.

Here's an example of one of those errors:

{
    "name": "validation_error",
    "message": "The `scheduled_at` field must be a future date",
    "statusCode": 422
}

It would be super helpful if we could get this data instead of a generic 'Failed to parse Resend API response'.

(regarding the first post, there are times where I get the error message but there's no errors on the logs, my question is still the same :) )

[drish]

Hi!

I've been using Resend for the last 6 months, and it has been working very well (quite a pleasant experience)!

Occasionally I get a 'Failed to parse Resend API response. Please try again.'.

Does anyone know what might be causing these errors? Can it be because of rate-limiting? I want to fix these, and I want to retry when I get an error like this, however, without knowing the potential cause (like rate-limits) I can't be as precise as I would like for the fix!

Thank you!

(I was using version 2.5.1, I've now bumped it to 2.10.0, however, looking at the changelogs, I don't believe it will fix these or give me any more detail about the cause)

Hey @miguel-arrf 👋 thanks a lot for bringing this up, I don't think the underlying issue that happens when you see the Failed to parse Resend API response. Please try again.' is due to Rate limiting, since that error message happens specifically when the API does not send json, it could probably be a network hiccup or the API had some sort of instability and the gateway responded with something other than json.

That being said though, we def need the RateLimit and the validation/422 error that you posted to be properly handled! I am pushing a PR improving the error handling

[drish]

@miguel-arrf just to be sure, are you not seeing any rate limit errors 429 on your resend logs correct ?