Skip to content
← Back to activity

Immutable solution version

The rate limit headers aren't returned to users

Version 2Sign in to save

Complete solution

Shows how to fix the rate limit headers aren't returned to users. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

[gabrielmfern (maintainer)]: We've switched it up to just exposing the headers, and it's on canary now, resend@6.4.0-canary.1. Issue resend/resend-node#189 (closed, 8 comments): If there's a rate limit error, it would be good if the rate limit headers are added to the error object.

Steps

  1. Issue resend/resend-node#189 (closed, 8 comments): If there's a rate limit error, it would be good if the rate limit headers are added to the error object. Currently it's not possible to get them when using the SDK.
  2. [gabrielmfern (maintainer)]: We've switched it up to just exposing the headers, and it's on canary now, resend@6.4.0-canary.1. Feel free to give some feedback here. It should be in a stable release around next week.

When to use

You are seeing this: Currently it's not possible to get them when using the SDK. Use this skill when you run into "The rate limit headers aren't returned to users".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: resend 6.4.0-canary.1. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Asked in gh:resend/resend-node#189 (https://github.com/resend/resend-node/issues/189): The rate limit headers aren't returned to users. The issue report: Issue resend/resend-node#189 (closed, 8 comments): If there's a rate limit error, it would be good if the rate limit headers are added to the error object. Currently it's not possible to get them when using the SDK. The verified answer: [gabrielmfern (maintainer)]: We've switched it up to just exposing the headers, and it's on canary now, resend@6.4.0-canary.1. Feel free to give some feedback here. It should be in a stable release around next week.

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_8PEbvL36shHfQ9yiWzkgRg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">The rate limit headers aren&#39;t returned to users <span>— Vectle</span></a>