Error: Attempted to use detached Frame '71AD84C72146516401939425D368CF3C'.

[kaualandi]

Are you using the latest version of the library?

• I have checked and am using the latest version of the library.

What type of session are you experiencing this issue on?

Multi-device and I have set multiDevice to true in my config OR am using the --multi-device flag

What type of host account are you experiencing this issue on?

Personal account (normal)

Mode

My own code

Current Behavior

I am using it with the express.js plugin, and when I try to send a message to a group, I get this error. The strange thing is that it works at first. The problem occurs when it has been running for a while, and the same group starts to fail.

The error returned by client.getGroupInfo and client.sendText:
Error: Attempted to use detached Frame ‘3890B259A949AD464E36129D2E05C1B0’.

Repository: https://github.com/kaualandi/wa-bot-express

Expected Behavior

No response

Steps To Reproduce

1. Use this code
2. Run with pm2 (default with fork mode)
3. After a while sending messages (every 5 minutes), it will give this error

create() code OR full CLI command + CONFIG

DEBUG INFO

import { Client, ConfigObject, NotificationLanguage } from "@open-wa/wa-automate"

export default function options(headless: boolean, start: (client: Client) => Promise<Client>) {
    const options: ConfigObject = {
        blockCrashLogs: false,
        disableSpins: false,
        hostNotificationLang: NotificationLanguage.PTBR,
        logConsole: false,
        //popup: true,

        viewport: {
            width: 1920,
            height: 1200
        },
        popup: 3012,
        multiDevice: true,
        defaultViewport: null,
        sessionId: 'wa-bot-express',
        headless: headless,
        qrTimeout: 0,
        authTimeout: 60,
        restartOnCrash: start,
        cacheEnabled: true,
        useChrome: true,
        killProcessOnBrowserClose: true,
        throwErrorOnTosBlock: true,

    }
    return options
}

Environment

- OS: Ubuntu 24.10
- Node: 22.17.0
- npm: 10.9.2

Screenshots/Logs

Anything else?

No response

[smashah]

i have no idea what is going on here or even how to replicate it. i think your instance of chrome has an extension which might be causing this