Skip to main content
Best answer

Improving Discord integration to handle rate limiting errors in Zapier


Forum|alt.badge.img

I’ve been regularly getting the below error message with my Discord integration, even though there is no delay before it in my Zap. I have since added a delay with an error handler after it, but that delay only gets triggered if I get this error, which I’ve been getting quite frequently.

When I look at the logs, it seems like this is an internal issue at Zapier, as Discord is rating limiting this request, even though this is the very first Discord action in my Zap:

{ "message": "You are being rate limited.", "retry_after": 0.3, "global": true }

I believe the global being true part means it’s Zapier’s bot going over 50 requests per second, which is not something I can control. Can Zapier update their Discord integration to cache the requests if they fail and retry them or something?

I believe my only workaround is to build my own Discord bot, which somewhat negates the point of the Discord Zapier integration and even if I did that, it’d increase the amount of actions this would require, which doesn’t seem right.

Best answer by ken.aBest answer by ken.a

Hi ​@Alex_Gillon,

It looks like that’s an error we’ve been running into is a known bug with Discord. Our team is aware of the issue and is working on a fix. I've added your email address as another affected user. That does a few things:

  • Bring this to the attention of the integration developers
  • Help track and prioritize fixes
  • Allows us to notify you via email if/when this is fixed

Unfortunately, I do not have an ETA, but I’ve added you to the list of users affected by this issue so we can let you know as soon as we have any updates.

I appreciate your patience and understanding.

View original
Did this topic help you find an answer to your question?

2 replies

ken.a
Forum|alt.badge.img+6
  • Zapier Staff
  • 6313 replies
  • Answer
  • January 28, 2025

Hi ​@Alex_Gillon,

It looks like that’s an error we’ve been running into is a known bug with Discord. Our team is aware of the issue and is working on a fix. I've added your email address as another affected user. That does a few things:

  • Bring this to the attention of the integration developers
  • Help track and prioritize fixes
  • Allows us to notify you via email if/when this is fixed

Unfortunately, I do not have an ETA, but I’ve added you to the list of users affected by this issue so we can let you know as soon as we have any updates.

I appreciate your patience and understanding.


  • New
  • 1 reply
  • February 12, 2025

@ken.a Can confirm we have Zaps affected by this as well