Saving scenario error: request entity too large

Questions & Answers
1

Hi all. I meet problem with make, for some reason i can’t save my scenario and got this message as report “Bad Request: request entity too large”

This is my scenario, it is quite large, can’t fit on one screen - https://i.imgur.com/CY7rqLr.png
This is error i receive when trying to save it - https://i.imgur.com/oNUVU4B.png

I contact support but not get respond yet. Any help would be greatly appreciate! Thanks.

Best,
Manojlo

2

Hi @Gigatron ,

its like the error states unfortunately, your scenario is too big. I have discussed this with support earlier already and it seems like the backend system currently can only support 2MB of data.

I quote the following from support:

In regards to the payload too large error please note we don’t have any limitations for the number of modules in a scenario, which means that technically, you can add as many modules as you need in order to design your ultimate workflow. However, there is a 2 MB limitation to a scenario blueprint (which is the scenario itself comprising all settings, described in our own meta-language). Once this limitation is reached, the “Payload Too Large” warning is displayed and you cannot save your scenario.

This means you have to split your scenario into multiple scenarios. You can then trigger them via HTTP and webhooks.

This is a great practice and I personally think this should always have to be done no matter what. handling these big scenarios could be a huge issue later on.

1 Like
3

Thank you for fast response, as you suggest I’ll split scenario. Anyway, I chose to build it huge and non-destructive in one scenario so if in the future we have any changes in the company, it’s easier to change one scenario module and automatically implement it on everything. Once again, big thank you for fast response, appreciate your help!

Best regards,
Manojlo

4

Hey @Gigatron ,

I understand the reason why you went for the 1 megatron scenario, however I would not say this is a best practice :wink:

You can achieve this as well when using multiple scenarios. Make sure you look at the following things for example:

  • Data stores to save and retrieve things (configurations, data records, history etc.)
  • Organization and Team variables which can hold data and to be used everywhere
  • Use the main scenario as “data handler” and “processor” then send the data which is required via HTTP to other scenarios. In this case you only need to modify the main scenario in case something changes somewhere.

Feel free to let us know how it went and what you achieved :wink:
Always interesting to see .

1 Like