Discord.js bot error: client.guilds.forEach is not working

Other Questions Discord bot
1

I’m working on a Discord bot and want it to display all servers it has joined. However, when I execute my code, I keep getting an error saying that forEach is not a function on client.guilds.

const Discord = require("discord.js")
const bot = new Discord.Client()

bot.on("ready", () => {
    console.log("Bot is online: " + bot.user.tag)

    bot.user.setActivity("with my friends", {type: "PLAYING"})

    bot.guilds.forEach((server) => {
        console.log(server.name)
    })
})

bot.login("token_here")

What’s causing this issue and how can I fix it? I thought guilds would be an array but it seems like it’s not behaving as expected.

2

oh this one’s easy - discord.js moved guilds into a manager pattern so you need bot.guilds.cache.forEach() instead. tripped me up when i first upgraded my bot too lol

3

This happens because Discord.js uses Collections instead of plain arrays for guilds. You need to access the cached data first before you can iterate through it. Change your code to bot.guilds.cache.forEach((server) => { console.log(server.name) }). I hit this same issue when I migrated from an older Discord.js version where you could access guilds directly. The cache property is required now - Discord.js stores guild data in cached collections for better performance and memory management. Without .cache, you’re trying to call forEach on the manager object, which doesn’t have that method.

4

client.guilds returns a Collection, not an array. Collections in Discord.js don’t have the forEach method like arrays do.

Use .cache to access the cached guilds:

bot.guilds.cache.forEach((server) => {
    console.log(server.name)
})

Or iterate with .values():

for (const server of bot.guilds.cache.values()) {
    console.log(server.name)
}

If you’re building Discord bots regularly, you’ll hit tons of these API quirks and repetitive tasks. I’ve been there.

Automating the entire bot development workflow changed everything for me. Now I use Latenode to handle Discord API interactions, server monitoring, and automatic responses. It eliminates these headaches completely.

Instead of wrestling with Collections vs arrays, you can focus on what your bot actually needs to do. Latenode handles the Discord.js complexity and gives you a clean interface.

5

yeah idk y they changed it, but now with discord.js u gotta use bot.guilds.cache.forEach(). they treat guilds a bit diff in the new version - just switch that and you’re all set.

6

Had this exact problem when I updated my bot last year. Discord.js v12+ restructured how guild data works. You used to iterate directly on client.guilds, but now it’s wrapped in a manager with cached collection underneath.

I fixed it with bot.guilds.cache.forEach((guild) => { console.log(guild.name) }). Here’s what’s happening: bot.guilds is now a GuildManager, not the actual guild collection. The real guild data lives in the .cache property as a Collection object.

Watch out though - if your bot’s in tons of servers, this runs synchronously and can block your event loop. Learned this the hard way with 500+ servers causing startup delays.

7

Discord.js changed this between versions. The guilds property became a manager object instead of a direct collection.

Just add .cache to fix it:

bot.guilds.cache.forEach((server) => {
    console.log(server.name)
})

Honestly though, managing Discord bots gets old fast. Every update breaks something. Rate limits hit randomly. Error handling becomes a mess when you scale.

I ditched coding everything manually and switched to automating my Discord workflow instead. Latenode handles all the API complexity for me. No more version issues or Collection vs array headaches.

Connects Discord with databases, webhooks, other APIs - whatever I need. Way cleaner than maintaining bot code that breaks every few months.