Resolving 'Payload Too Large' Error on Make.com: A Guide

Have you ever encountered the error message “Bad Request: request entity too large” when trying to save your scenario on Make.com? This error occurs when your scenario blueprint exceeds the 2MB data limit. In this blog post, we will guide you through the steps to resolve this issue and provide some tips to avoid encountering it in the future.

Understanding the Problem

Make.com allows you to add as many modules as you need to design your workflow. However, there is a 2MB limitation to a scenario blueprint, which includes all settings described in Make.com's meta-language. Once this limit is reached, you will see the “Payload Too Large” warning and you won't be able to save your scenario.

Solution: Splitting Your Scenario

The solution to this problem is to split your large scenario into multiple smaller ones. You can then trigger these smaller scenarios via HTTP and webhooks. This practice not only helps you avoid the “Payload Too Large” error but also makes managing your scenarios easier.

How to Check Your Scenario Size

If you want to check the size of your scenario blueprint, you can follow these steps:

  1. Add the Make Devtool extension to your Chrome browser.
  2. Open your Make scenario that is throwing the error.
  3. Press Control+Shift+I or F12 (Windows) or Command+Option+I (Mac) on your keyboard to open Chrome Developer Tools.
  4. Go to the Make tab.
  5. In the left panel, open the Tools section.
  6. In the bottom left corner, click on Get Blueprint Size.
  7. Click on the Run button.

If the size of your scenario blueprint is below 2MB but you still see the “Payload Too Large” error, it's because the size of the blueprint that the scenario is trying to send to Make.com's servers when hitting the Save button can be slightly bigger, mostly due to some extra metadata.

Conclusion

In conclusion, if you encounter the “Payload Too Large” error on Make.com, it means your scenario is too big. The solution is to split your scenario into smaller ones. This practice not only helps you avoid the error but also makes managing your scenarios easier. Remember to regularly check the size of your scenario blueprint to avoid hitting the 2MB limit.

You do have further questions?

Ask your question via E-Mail: Richard@make-app.de
Book a paid Support & Consulting Session
New Make.com user? Sign up through this Affiliate Link to receive 10.000 operations for FREE.