Discord node response ERROR: Cannot read properties of undefined (reading 'retry_after')

Describe the issue/error/question

I often use Discord + RSS to get a lot of information, and I’m glad that Discord can now send embedded content!

I upgraded from the old version 0.127.0 to 0.174.0

In 0.127.0, the Discord node worked until all content was sent (my record here is 50!)
But in 0.174.0, if you send more than 5 contents/time, it will return an error message and stop running

What is the error message (if any)?

ERROR: Cannot read properties of undefined (reading 'retry_after')

Please share the workflow

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 0.174.0
  • Database you’re using (default: SQLite): Heroku Postgres
  • Running n8n with the execution process [own(default), main]:
  • Running n8n via [Docker, npm, n8n.cloud, desktop app]: docker

Thank you very much for reporting this @Han!

From looking into this it seems the Discord node is expecting a specific response format which Discord doesn’t use (anymore, presumably). I’ll add this to our internal bug tracker for a closer look.

The root cause for the problem would be too many messages being sent to Discord at once and Discord responding with a 429 status. This could be avoid by sending less messages at once, for example by building a small loop including the Wait node. Here is an example sending one message every 2 seconds which seems to work fine for me:

Result after processing all 50 items:

Could you give this a go on your side and let me know if you are still facing any issues afterwards?

So that’s the way to connect, I learned a lesson, thanks! (The way that loop works is so cool! :open_mouth:)

Does n8n Team have any plans to increase the delay between sending messages a little bit?

1 Like

I think that’s what should usually happen if it wasn’t for the bug (n8n taking the required wait time from Discourse and respecting it). Once that’s fixed n8n should wait as long as needed.

1 Like