Skip to main content
Best answer

Set delay to positive integer error message on Discord "Add Role" step

  • February 6, 2025
  • 1 reply
  • 3 views

My automation has been working flawlessly since it was created. (I had not changed anything)

Recently, it started getting this random error on the Discord “Add roll” step.
It told me to set the delay to a positive integer - except I didn't build this automation with any delays in it at all. So I figured that was its way of telling me to add a delay.

I added “Delay For” > Set it to a positive integer, but that still didn't work.  I found a reddit post where someone said that Zapier support suggest to change from “Delay for” to “Delay after queue” - which i did and also set it to a positive integer. - I am still getting the error.

The biggest annoyance with this is that it is NOT happening on every single role assignment. Its happening on seemingly random users. There is no way for me to identify why nor how its deciding who its going to throw this error for.
I would understand if maybe it was getting overloaded because its running for tons of users at a time, but that isn't the case at all. The join rate isn't consistent. It varies. But before this, it didn't matter anyway. It always worked without a delay. 

I did come across another person in this community with same exact issue and saw that someone commented saying that its an issue on Zapier's end that is being looked at. I would like to be added to the list of users that this issue is effecting if possible/ if not solved. 


Quick run down of my full Automation (if needed)

Typeform "New Entry" > Filter by Zapier "Filter Conditions" > Formatter by Zapier "Text" > Discord "Find User" > Delay by Zapier "Delay After Queue" > Discord "Add Role" > Discord "Send Channel Message" > Airtable "Create Record" > Airtable "Create Record" 

(Before the error started happening the only thing different about this automation is that “Delay by Zapier” was not in my automation. It worked completely fine.)

Other then this delay error and it not adding a role, every other thing is working correctly in my steps. 

 

Best answer by ken.a

Hi there ​@GodMo-Sonder,

Welcome to the Community! 🎉

It appears you might be running into a bug where we are being rate limited by Discord. This rate limiting has to do with all requests via Zapier, not just those from your account, unfortunately. My suggestion here would be to enable Auto-replay so that the failed Zap run can be reattempted at a later time, to attempt to circumvent these rate limits. Our team is aware of the issue and is working on a fix. I've added your email address as another affected member. 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.

In the meantime, you can stay in the loop/follow along with updates on the main thread here: 

I appreciate your patience and understanding.

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

1 reply

ken.a
Forum|alt.badge.img+6
  • Zapier Staff
  • 6301 replies
  • Answer
  • February 7, 2025

Hi there ​@GodMo-Sonder,

Welcome to the Community! 🎉

It appears you might be running into a bug where we are being rate limited by Discord. This rate limiting has to do with all requests via Zapier, not just those from your account, unfortunately. My suggestion here would be to enable Auto-replay so that the failed Zap run can be reattempted at a later time, to attempt to circumvent these rate limits. Our team is aware of the issue and is working on a fix. I've added your email address as another affected member. 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.

In the meantime, you can stay in the loop/follow along with updates on the main thread here: 

I appreciate your patience and understanding.