# Instance creation generates empty, non-functional instances #2419

Welcome!

• Yes, I have searched for similar issues on GitHub and found none.

What did you do?

Description

Since updating to evo-api version 2.3.7, newly created instances are generated empty and without any functionality.

The instance creation process does not return any visible errors. However, the resulting instance is unusable and remains in a close state, without proper initialization or operational features.

Below is an example showing how the created instance appears in the system, despite being non-functional:

Request Payload

This is the object sent by evo-api when creating the instance:

{
    "instanceName": "Yo",
    "integration": "WHATSAPP-BAILEYS",
    "token": "0DF83334338C-4D4B-94A5-70526B46F058",
    "number": "573192107643"
}

API Response

And this is the response returned by the API:

{
    "instance": {
        "instanceName": "Yo",
        "instanceId": "4b8c6a0a-b292-4ceb-88a1-f69fcee0c40b",
        "integration": "WHATSAPP-BAILEYS",
        "webhookWaBusiness": null,
        "accessTokenWaBusiness": "",
        "status": "close"
    },
    "hash": "0DF83334338C-4D4B-94A5-70526B46F058",
    "webhook": {},
    "websocket": {},
    "rabbitmq": {},
    "nats": {},
    "sqs": {},
    "settings": {
        "rejectCall": false,
        "msgCall": "",
        "groupsIgnore": false,
        "alwaysOnline": false,
        "readMessages": false,
        "readStatus": false,
        "syncFullHistory": false,
        "wavoipToken": ""
    }
}

Observed Behavior

• The instance is created successfully according to the API.
• No errors are returned.
• The instance remains in close status.
• The instance lacks expected functionality and cannot be used.

Expected Behavior

• The instance should be fully initialized after creation.
• It should be able to connect and operate normally.
• The status should change accordingly (e.g., open, connecting, etc.).

What did you expect?

I would appreciate it if you could provide at least one stable version where this issue does not occur, so I can temporarily downgrade while the problem is being investigated.

The instance should be fully initialized after creation.

It should be able to connect and operate normally.

The status should change accordingly (e.g., open, connecting, etc.).

What did you observe instead of what you expected?

What has happened since we uploaded the version?

Screenshots/Videos

No response

Which version of the API are you using?

2.3.7

What is your environment?

Linux

Other environment specifications

node 22
ubuntu 24.04

If applicable, paste the log output

No response

Additional Notes

No response