We are trying to enable document uploads in our Web Messaging implementation. The requirement is simple: customers send PDFs for processing. I’ve configured the queue settings in the Admin UI to allow file attachments. However, when testing with the genesys-cloud-web-messaging SDK, any PDF over 2MB fails immediately. The SDK logs show a 413 Payload Too Large error from the API gateway before the file even hits our backend logic.
I’ve checked the documentation for the /api/v2/webmessaging/attachments endpoint. The docs state a 10MB limit for attachments. I’m sending a 3MB PDF. It shouldn’t fail. Here is the configuration object I’m passing to the chat initialization:
const config = {
organizationUuid: 'our-org-uuid',
queueUuid: 'our-queue-uuid',
customAttributes: {
source: 'web' // just for tracking
},
// trying to set limits explicitly, though docs say it's server side
maxFileSize: 10485760 // 10MB in bytes
};
The maxFileSize property isn’t even listed in the TypeScript definitions for the SDK config, so it gets ignored. The actual error comes from the WebSocket layer when the SDK tries to upload the blob. The response payload from the error callback looks like this:
{
"code": 413,
"message": "Request entity too large",
"details": "Upload size exceeds configured threshold for this queue"
}
I’ve verified the queue settings in the UI. The “Allow file attachments” toggle is ON. There is no field for setting a specific size limit in the UI, only the toggle. Is there a separate API call required to increase the threshold per queue? Or is this a global org setting I’m missing? I’ve searched the Admin API docs for webmessaging and attachments but found nothing about size configuration endpoints. Just the data retrieval ones. This is blocking our rollout. Need to know if this is a hard-coded limit on the platform side or if I’m missing a configuration step in the code.