Hi there ​@illinoisTKD,

I moved your reply to a new post. I hope you don’t mind!

Before we dig deeper into this, would you mind sharing a detailed screenshot of how your Zap is configured? Also, please share a screenshot of the CONFIGURE section of the Discord step that shows all of its fields.

Please don't include personal information in the screenshot, or be sure blur out any personal information.

Thanks!

Hi ​@illinoisTKD,

Thanks for the screenshot!

I looked into this issue and it seems that you're being rate-limited due to our global limits for the Discord integration. 
 
A rate limit means that you're exceeding the maximum amount of requests that one app allows per account, and after inspecting the logs and Discord's documentation, we can see that it's hitting the global rate limit of 50 requests per second.
 
You can find more information about it here: https://discord.com/developers/docs/topics/rate-limits#global-rate-limit
 
We are not able to increase this limit for you, but it resets after a few seconds and requests can be retried successfully.
 
Please note that every request sent from Zapier to your Discord account will contribute to the limit, including requests that don't result in a specific action or trigger. Other integrations with Discord's API, that don't happen through your Zapier account will also contribute to it.

Hopefully, this helps!

I’m confused, because it’s literally one step in the Zap. Why is it recording as 50 requests? My other Zaps that include a step involving a Discord message never disconnect. How can we resolve this?

Hi ​@illinoisTKD,

You’re completely correct. It looks like this is a bug where Discord is hitting the global rate limit on Zapier requests. I have added you to the open bug report. While we can’t provide an ETA for the fix. We will let you know once the bug has been fixed.

I appreciate your patience and understanding.

Hello, I can confirm that I am experiencing the same problem.

When I re-run this Zap after it errors out sometimes it works.

Can I ask the Zap to re-run if an error occurs?

Has this bug been solved by now?

Hi ​@rashednaber,

We sincerely apologize, but the ticket is still open as of now. I’ve added you to the list of affected users, and we’ll notify you via email once an update is readily available. Thanks.

I have the same issue! Any Bug Fix soon?

I have had temporary fix which is if you keep trying to log in sometimes it works for a while.

I know its not a fix but it works sometimes sorry I hope it somewhat helps cause it has worked for me.

Hi folks

​@hektoven - I’ve added you to the list of folks that are being impacted by this so you’ll get an email notification as soon as it’s resolved. As Ken and Jammer mentioned earlier in this thread, we can’t give any sort of ETA on when you can expect a fix to be put in place. 

Hopefully ​@rashednaber’s solution of replaying any errored Zap runs a bit later on helps—thanks so much for sharing that tip, ​@rashednaber!  To save you having to log back in and manually replay them you might want to try out Autoreplay feature (available on Professional or higher plans) which will attempt to replay them automatically.

Also, wanted to suggest adding a Delay After Queue (Delay by Zapier) action ahead of the Discord action in your Zaps. That should help to space out the requests that are being made to Discord’s API and hopefully avoid the errors. If you’d not used that type of action before you can learn more about it here: Delay after queue.

Hope that helps and thanks for your patience in the meantime! 

You're hitting Discord's rate limit, which means too many messages are being sent too quickly. Try adding a delay step in Zapier or reducing the frequency of the messages. Zapier doesn’t always show these errors clearly, so checking logs like you did is the right move.

Make sure the Discord bot has the correct permissions to post in that channel, and double-check the channel ID used in the Zap. Also, verify the bot is still connected to your server.

Hi, I’m experiencing this issue as well. This is very likely to be an issue with the Zapier discord bot itself exceeding the rate limit for all the servers it is in, it might be worth it for the developer to shard the bot so it runs different instances in different sets of servers.

Hi ​@jordan8,

I’ve added you to the list of affected users, and we’ll notify you via email once an update is readily available. Thanks.

Hi, I’m experiencing this issue as well. i got this code when im trying to launch calendly to discord 

Unable to turn on "ADR - Calendly to Discord"
('Discord throttling https://discord.com/api/v10/guilds/1324460308714094703', 1)

Hi ​@Skynox,

I’ve added you to the list of affected users, and we’ll notify you via email once an update is readily available. Thanks.

Has there been any update to this? I am also experiencing the issue.

Hi ​@Aesir,

Currently there is no update yet regarding with this bug. But I added you to the list of affected user so we can send an email once an update is available. Thank you.