sendText requests hanging for specific instances

[emilio-kalificado]

Welcome!

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

What did you do?

I am experiencing an issue with Evolution API where certain instances intermittently fail when using the sendText endpoint.

When I check the instance status, it appears as active/connected.

Other actions work correctly, including verified user checks and sending typing indicators.

However, when I call the sendText endpoint, the request hangs indefinitely. It does not return an error and does not return any response. It simply stays pending until it times out.

This does not happen to all instances. Some instances work normally, while others hang on sendText. The behavior is intermittent and rotates between instances. An instance that previously failed may start working again, and another instance that was working may start failing.

I am running approximately 60 instances. Each instance has its own dedicated proxy. The service is deployed in a containerized environment.

Are there any known limits or best practices when running 50+ instances?
Could this be related to concurrency limits, socket saturation, or internal queue handling?
Is it recommended to split instances across multiple containers or services in this scenario?

What did you expect?

I expected the sendText endpoint to return a successful response and deliver the message immediately for any instance that is marked as active

What did you observe instead of what you expected?

The sendText request hangs indefinitely with no response or error, even though the instance appears active and other actions (like verified user checks and typing indicators) work correctly. The issue only affects some instances and rotates between them.

Screenshots/Videos

No response

Which version of the API are you using?

2.3.7

What is your environment?

Linux

Other environment specifications

Running around 60 instances in the same VPS
Each instance has it's own proxy

If applicable, paste the log output

No response

Additional Notes

No response

[cleytoncoro]

It looks like a network problem.
I usually see this while using bad proxies.

[MarcoRivas22]

I've had the same problem for two days.