DIA
discord.js - Imagine an app•3w ago
Black Wolf

"No Description" when calling for guild.channels.fetchActiveThreads()

Get "https://discord.com/api/v10/guilds/1334649246472732712/threads/active?": context deadline excee... 
DiscordAPIError[undefined]: No Description
    at handleErrors (/app/node_modules/@discordjs/rest/dist/index.js:727:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async SequentialHandler.runRequest (/app/node_modules/@discordjs/rest/dist/index.js:1128:23)
    at async SequentialHandler.queueRequest (/app/node_modules/@discordjs/rest/dist/index.js:959:14)
    at async _REST.request (/app/node_modules/@discordjs/rest/dist/index.js:1272:22)
    at async GuildChannelManager.fetchActiveThreads (/app/node_modules/discord.js/src/managers/GuildChannelManager.js:487:18)
    at async retryFetch (file:///app/src/utils/discord-archiver.js:17:14)
    at async getActiveThreads (file:///app/src/utils/discord-archiver.js:37:21)
    at async processGuildThreads (file:///app/src/utils/discord-archiver.js:355:27)
    at async Promise.all (index 1) {
  requestBody: { files: undefined, json: undefined },
  rawError: ArrayBuffer {
    [Uint8Contents]: <47 65 74 20 22 68 74 74 70 73 3a 2f 2f 64 69 73 63 6f 72 64 2e 63 6f 6d 2f 61 70 69 2f 76 31 30 2f 67 75 69 6c 64 73 2f 31 33 33 34 36 34 39 32 34 36 34 37 32 37 33 32 37 31 32 2f 74 68 72 65 61 64 73 2f 61 63 74 69 76 65 3f 22 3a 20 63 6f 6e 74 65 78 74 20 64 65 61 64 6c 69 6e 65 20 65 78 63 65 65 ... 3 more bytes>,
    byteLength: 103
  },
  code: undefined,
  status: 408,
  method: 'GET',
  url: 'https://discordproxy.local.blackwolfwoof.com/api/v10/guilds/1334649246472732712/threads/active'
}
DiscordAPIError[undefined]: No Description
    at handleErrors (/app/node_modules/@discordjs/rest/dist/index.js:727:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async SequentialHandler.runRequest (/app/node_modules/@discordjs/rest/dist/index.js:1128:23)
    at async SequentialHandler.queueRequest (/app/node_modules/@discordjs/rest/dist/index.js:959:14)
    at async _REST.request (/app/node_modules/@discordjs/rest/dist/index.js:1272:22)
    at async GuildChannelManager.fetchActiveThreads (/app/node_modules/discord.js/src/managers/GuildChannelManager.js:487:18)
    at async retryFetch (file:///app/src/utils/discord-archiver.js:17:14)
    at async getActiveThreads (file:///app/src/utils/discord-archiver.js:37:21)
    at async processGuildThreads (file:///app/src/utils/discord-archiver.js:355:27)
    at async Promise.all (index 1) {
  requestBody: { files: undefined, json: undefined },
  rawError: ArrayBuffer {
    [Uint8Contents]: <47 65 74 20 22 68 74 74 70 73 3a 2f 2f 64 69 73 63 6f 72 64 2e 63 6f 6d 2f 61 70 69 2f 76 31 30 2f 67 75 69 6c 64 73 2f 31 33 33 34 36 34 39 32 34 36 34 37 32 37 33 32 37 31 32 2f 74 68 72 65 61 64 73 2f 61 63 74 69 76 65 3f 22 3a 20 63 6f 6e 74 65 78 74 20 64 65 61 64 6c 69 6e 65 20 65 78 63 65 65 ... 3 more bytes>,
    byteLength: 103
  },
  code: undefined,
  status: 408,
  method: 'GET',
  url: 'https://discordproxy.local.blackwolfwoof.com/api/v10/guilds/1334649246472732712/threads/active'
}
This is when guild.channels.fetchActiveThreads()) tries to run and fails. I am guessing it might be way too big the request. I only want to have the channel ids & amount of the active threads, nothing else.
17 Replies
d.js toolkit
d.js toolkit•3w ago
- What's your exact discord.js npm list discord.js and node node -v version? - Not a discord.js issue? Check out #other-js-ts. - Consider reading #how-to-get-help to improve your question! - Explain what exactly your issue is. - Post the full error stack trace, not just the top part! - Show your code! - Issue solved? Press the button!
Black Wolf
Black WolfOP•3w ago
[email protected] node: v23.11.0 As a note, i am using my own discord proxy here
Mark
Mark•3w ago
:Thonk: what is that url in the error, that doesn't look like it's coming from discord
Black Wolf
Black WolfOP•3w ago
which url
Mark
Mark•3w ago
  status: 408,
  method: 'GET',
  url: 'https://discordproxy.local.blackwolfwoof.com/api/v10/guilds/1334649246472732712/threads/active'
}
  status: 408,
  method: 'GET',
  url: 'https://discordproxy.local.blackwolfwoof.com/api/v10/guilds/1334649246472732712/threads/active'
}
at the bottom of your error stack
Black Wolf
Black WolfOP•3w ago
^
Mark
Mark•3w ago
i didn't realize it modified the url like that, huh
Black Wolf
Black WolfOP•3w ago
imagine discordproxy.local.blackwolfwoof.com to be discord.com its a 1:1 proxy I use it to monitor if my bots blow up and to handle ratelimits
Black Wolf
Black WolfOP•3w ago
Black Wolf
Black WolfOP•3w ago
-# https://github.com/germanoeich/nirn-proxy if you are interested 408 suggests a timeout Honestly i haven't tried it without my proxy yet
Mark
Mark•3w ago
that proxy has been identified as the cause of timeouts in other projects
Black Wolf
Black WolfOP•3w ago
oh no aaa, welp. Lemme skip it in my bot.js and come back after some testing (1-2d) I really hope its not that because i like it. It does its job very well Dunno if it is better but i now get these
Black Wolf
Black WolfOP•3w ago
Black Wolf
Black WolfOP•3w ago
basically the same moment the old errors hit
Black Wolf
Black WolfOP•3w ago
d.js docs
d.js docs•3w ago
AbortError: The user aborted a request. A request took longer than the specified timeout (15 seconds default), and was aborted to not lock up the request handler. - This can be caused by an internal server error on Discord's side, or just a slow connection. - In case of a slow connection, the timeout option in RESTOptions can be increased to prevent future AbortErrors.
Black Wolf
Black WolfOP•3w ago
15 seconds is wild though to query threads thats way too long is there any other way i could get all active threads? Maybe by for example looking at the guild object and then asking each channel for threads? Will kinda suck as thats lots of api calls and shit Ig imma double the timeout and see if that request really takes so long. I doubt it tbh but yea

Did you find this page helpful?