Absolutely! Mallabe is fully equipped to handle large images. In fact, we've successfully managed images as large as 20,000 x 20,000 pixels.

However, managing such large images necessitates a specific architecture for your workflow. This is crucial because Mallabe gateway has a timeout limit of 29 seconds. Exceeding this limit will result in a “504 Gateway Timeout” error. Therefore, careful consideration of your workflow architecture is essential for seamless operation.

The gateway timeout configuration represents a concrete limitation within our foundational infrastructure, residing atop Amazon Web Services (AWS). It mandates that all responses must be delivered within a strict 29-second window, with no possibility of alteration. Further details can be found in the AWS documentation provided here.

Despite the gateway timing out after 29 seconds, rest assured that the application will persist in processing your images. The challenge lies in the fact that you won't receive notifications of this ongoing process. However, there is a solution available.

If You Are Using Make (formerly Integromat)

Your workflow will need to be divided into two separate processes:

  1. A new flow that receives requests from Mallabe - this can involve either the "Watch Image Resize" or "Watch Image Compress" trigger, depending on your workflow.

    https://tidio-images-messenger.s3.amazonaws.com/ozbdrimnhdmec3oucu580m1ut2acp6i1/images/7c4a346d-00cc-4c50-8f92-3c29ee54cfd0.png

    https://tidio-images-messenger.s3.amazonaws.com/ozbdrimnhdmec3oucu580m1ut2acp6i1/images/5956b6cf-e76c-4fe1-9d87-5fec5cea2ff8.png

  2. A flow that sends a request to Mallabe - you might already have this step in place, but instead of directly sending the request to Mallabe and waiting for a response, you would send an "Advanced" request (by enabling the “Show advanced settings”), and require Mallabe to send responses to the webhook URL provided in the first flow.

    Untitled

<aside> 💡 Note: Despite implementing this two-flow mechanism, your second flow may still encounter "504 Gateway Timeout" errors. However, it's important to disregard these flow errors.

</aside>

<aside> 💡 Note: To prevent potential timeouts caused by Make limitations, it is crucial to maintain the two-step solution in separate scenarios. Avoid combining both steps within the same scenario.

</aside>

Make Webhooks

For further guidance on Make Webhooks, refer to the help pages here and watch the following video:

https://www.youtube.com/watch?v=2I1RcZ4q_58

Please note that while the video discusses webhooks in a general context, Mallabe already provides triggers like "Watch Image Resize" and "Watch Image Compress," which directly implement webhooks for your convenience.