-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Message ain't receiving in some, if the group is not active for 1 or 2 hrs #1146
Comments
I don't know if this is the error, but I am experiencing a similar situation. Some messages are sent, while others are not. There is no error message either.
|
the latest version is v6.7.9, test that first before posting an issue here |
I already use 6.7.9
|
6.7.9 is showing worse errors. Replying to old messages. |
sama problem, up |
Bug Report: Bot Becomes Unresponsive in Inactive Groups
Description
The bot, built using Baileys v6.7.8, becomes unresponsive in WhatsApp groups that have been inactive for 1-2 hours. This issue is resolved only after restarting the bot. It appears to be related to socket management or connection stability during prolonged group inactivity.
Environment Details
Baileys Version: 6.7.8
Node.js Version: 20
Operating System: Linux (inside a Docker container)
Environment: Dockerized application
Socket Configuration
const connectionOptions = {
version: version, // [2, 3000, 1015901307]
logger: Pino({
level: 'silent',
}),
printQRInTerminal: true,
browser: Browsers.ubuntu("Chrome") || ["Ubuntu", "Edge", "110.0.1587.56"] || Browsers.macOS("Safari"),
auth: {
creds: state.creds,
keys: makeCacheableSignalKeyStore(state.keys, pino({ level: "fatal" }).child({ level: "fatal" })),
},
markOnlineOnConnect: true,
generateHighQualityLinkPreview: true,
getMessage: async (key) => {
let jid = jidNormalizedUser(key.remoteJid);
let msg = await store.loadMessage(jid, key.id);
return msg?.message || '';
},
msgRetryCounterCache,
defaultQueryTimeoutMs: undefined,
};
Any solution?
The text was updated successfully, but these errors were encountered: