mentionAll + media: Sending media with mentionAll causes failure / requires split workaround

[netoduwe]

Welcome!

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

What did you do?

I integrated Evolution Go into a WhatsApp group management platform that sends scheduled and manual messages.

When sending a media message (image/video/document) together with mentionAll enabled, the provider does not behave correctly in a single /send/media call.

Example scenario:

• send an image/document
• include caption text
• enable mentionAll=true

In our integration, we had to add a provider-specific workaround for Evolution Go:

1. send media without caption/mentions
2. send a second text message with mentionAll separately

This workaround was added because combining media + caption + mentionAll in one request appears to fail.

What did you expect?

I expected Evolution Go to support sending media together with caption text and mentionAll in a single request, without requiring a split workaround.

What did you observe instead of what you expected?

When media + caption + mentionAll are combined in a single send/media flow, Evolution Go does not behave correctly.

In our integration, we had to avoid the native combined payload and instead split it into two messages:

• first: media only
• second: text with mentionAll

This suggests that the combined media + mentionAll flow is not reliably supported in Evolution Go.

Screenshots/Videos

No response

Which version are you using?

latest

What is your environment?

Linux

If applicable, paste the log output

No response

Additional Notes

This appears to be provider-specific behavior in Evolution Go.

We documented and implemented a workaround in our integration layer:

• for Evolution Go, when mentionAll is used together with media/caption, we split the send into two messages

It would be helpful to clarify:

1. whether media + mentionAll in a single request is officially supported
2. whether caption + mentionAll is expected to work with /send/media
3. whether there is a recommended payload format for this use case