Hi Zapier team, while I understand the difficulty of giving an exact ETA, are you able to let us know if this is actively being worked on by the team or is it in a backlog? My discord automation needs are scaling up and currently my zaps with discord role actions are only succeeding around 30% of the time.

While I’m here, I would also like to suggest the addition of a bulk role add action. I believe this is possible using the discord modify guild member api endpoint but I haven’t worked with the API before: https://discord.com/developers/docs/resources/guild#modify-guild-member

Hi ​@BrokenScience 

Sorry to hear that this is having such a big impact on your Zaps, especially as you’re trying to scale things up. I’ve added you to the list of affected users so you’ll be notified of any updates. Right now, this isn’t something our team is actively working on, but we’re continuing to track those being affected by it. Adding you to the list helps to further raise its visibility and priority.

Out of curiosity, if you replay the errored Zap runs a bit later, do they go through successfully? If so, and you’re on a paid Zapier plan, it might be worth enabling the Autoreplay feature as it would automatically replay any errored Discord actions for you.

While I’m here, I would also like to suggest the addition of a bulk role add action. I believe this is possible using the discord modify guild member api endpoint but I haven’t worked with the API before: https://discord.com/developers/docs/resources/guild#modify-guild-member

Being able to assign multiple roles to a Discord user at once would be a great feature to have added! Can you reach out to our Support team so that they can submit a feature request for that on your behalf: https://zapier.com/app/get-help. 🙏

In the meantime, perhaps you could try using an API Request action to make a call to that Modify Guild Member API endpoint. If you’ve not worked with API Request actions in Zaps before check out our Create an API Request action guide to get started. And if you run into any snags setting that up, please start a new topic—that’ll help to keep the discussion in this thread focused on the bug. Thanks!

Hey - this is also effecting us, and would be a reason to move away from Zapier as a paid customer elsewhere, because this is breaking one of our core use cases.

Thanks for reaching out here, ​@peraldon. I’m so sorry about the impact this bug is having on your core use case with Zapier. I’m unable to provide any sort of ETA on when you can expect it to be resolved, but I’ve added you to the list of folks being affected so we will notify you as soon as it’s resolved.

In the meantime, I’d recommend replaying the errored Zap runs a bit later on to see if they are then able to run successfully. Not an ideal solution I know, but if you’re on a paid plan you can turn on the Autoreplay feature to have them automatically replayed for you.

Thanks for everyone continued patience on this 

Hello SamB,

we are also experiencing this issue and we’re only trying to add ~50 roles of a single kind a day (that’s 2 roles per hour). I think the process of adding these roles might just be flawed on Zapier’s side. Why would the integration need to scan for all users on the Discord server to assign a role?

If I’d use a bot I’d send a single Rest API request to the bot with the account’s username and add it. If they’re not on the server push it into a backlog and repeat with an interval until they’re successfully added. Scanning servers with 100,000+ users just isn’t feasible imho.

Thanks for adding me to the list and checking this out with your development department. Appreciate you trying to solve this. 

Kind regards,

Joey

​@SamB Having the same problem, I can’t even test the trigger, as it results in:

Error while retrieving: ('Discord throttling https://discord.com/api/v10/channels/...’)

Reading this thread is very disheartening, I can see very little motivation or assurance given the number of people reporting this issue. As Discord is quite a popular powerful app in Zapier, it surprises me that all you can provide is a dismissal “this isn’t something our team is actively working on”.

Does Zapier prioritise working on other apps, especially when one is in a broken state for many users? 

Hi ​@jowe1 and ​@Eth 

Thanks for letting us know that you’re being affected by this bug as well. I’ve added you both to the list of folks being impacted which will ensure you get a notification as soon as it is resolved. 

I’m sorry that this issue has been around for so long and really wish I was able to provide a timeline on when it will be sorted. For context when we prioritize issues, we look at a number of things like how many users are impacted, how severe the issue is and how complex the fix is. While I’m not able to give any sort of timeline for when it will be resolved, I’ll be sure to post an update here if anything changes on the status of the bug.

As a temporary solution, if replaying the errored runs doesn’t work then it may be worth exploring using the Webhooks app instead. It’s a more advanced app but I’d be happy to lend a hand if you run into any issues setting it up - just let me know!