Can we configure WAHA to use different engines

[MadhabaPatra]

@devlikepro I want to configure WAHA with multi engine such as NOWEB for some users and WEBJS for others under same api (SAME WORKER)? or what's the approach ?

[devlikepro]

Nope, we don't allow it to avoid any issues. The responses for engines a bit different, stores also, so it can create a mess pretty quickly. Usually people choose one engine and stick to it and if they need (we do) - they deploy it on different workers

Consider running it on different port or use a different subdomains, if you have it

https://waha-1.example.com/
https://waha-2.example.com/

or just

https://waha.example.com:3000
https://waha.example.com:3001

[MadhabaPatra]

I feel that the NOWEB engine is more sensitive (chances of blocking )compared to WEBJS, as WEBJS runs with a browser. What's your view on this? Additionally, certain features, like sending buttons, are only possible in NOWEB. However, some users want to send buttons, which led to my query.

[devlikepro]

like sending buttons

Wait, does it work for you? It haven't for few months for us 🤣 buttons are fragile creatures, it can stop working any time.

In that case - only two different workers.

[MadhabaPatra]

Honestly, I haven’t tried it yet. 😅 Do you mean that buttons are not fully functional at times? What’s your POV on this: The requirement is to send buttons to 100 users at random intervals. Do I really need NOWEB, or should I consider alternative ways (polls/simple text message) instead of buttons?

[devlikepro]

but polls not available in WEBJS, so yes, only NOWEB for now.
Consider creating a feature request for GOWS pollls support, we can add it too (GOWS has better performance/stability)