New workflow webhook size limit issue - even smaller size are not accepted

[vivekk0903]

Steps to reproduce

I am minifying an adaptive card json and sending to the new workflow webhook (created using the existing template "Post to a channel when an incoming webhook is recieved").

But the workflow run is failing with the message:

{"statusCode":400,"headers":{"Transfer-Encoding":"chunked","Vary":"Accept-Encoding", ... ,"body":{"error":{"code":"BadRequest","message":"InvalidParameter","innerError":{"code":"1","message":"MessageSizeExceeded-Message properties size exceeded. Actual message properties size: 28897 bytes, whereas max allowed size is 28672 bytes"}}}} ...

When I look at the size in request it shows this size:

{'User-Agent': 'python-requests/2.31.0', 'Accept-Encoding': 'gzip, deflate, br', 'Accept': '*/*', 'Connection': 'keep-alive', 'Content-Type': 'application/json', 'Content-Length': '24453'}

And I can see the same size in workflows run UI:

But it only fails when it reaches the second part:

Expected behavior

It looks like after the next step some inflation is happening in the json and its size is increasing. It should not happen so, and the workflow run should succeed.

Actual behavior

The workflow is failing

Error details

No response

[microsoft-github-policy-service[bot]]

Hi vivekk0903! Thank you for bringing this issue to our attention. We will investigate and if we require further information we will reach out in one business day. Please use this link to escalate if you don't get replies.

Best regards, Teams Platform

[Prasad-MSFT]

@vivekk0903 - Thanks for raising your issue. We will check this at our end and will update you accordingly.

[Prasad-MSFT]

Hi @vivekk0903 , could you please share the card JSON which you are using in this case?

[vivekk0903]

Yes, I have attached the json. example.json

I am posting it like this: requests.post(WEBHOOK_URL, data=JSON_READ_AS_STRING, headers={'Content-Type': 'application/json'})

[Prasad-MSFT]

@vivekk0903 , We have raised a bug for the same. We will inform you once we get any further update from engineering team.

Thanks!