Scenario doesn’t save

When I saved my scenario. I have a error - Connection error. Payload Too Large.
Help me, please )

Can you share a screenshot of the full flow for me?
and of the error?


Alrighty. First piece of advice: when scenarios get this big. break them into multiple scenarios with webhooks and HTTP modules. it should help you with general performance, and making sections “modules” that are reusable"

e.g. instead of having 5 “set user role” for each of the 5 different user roles, have 1 set user role flow as a scenario triggered by a webhook, and pass in the data telling that module, what role to set.

Projects are a lot more maintainable if you build them in a non(mono-lithic) approach, with reusable components, and tend to be more performant as well.

1 Like

Thank you very much!

1 Like

example from one of my workflows, scraping data, then making a decision on whether or not to push the data, each of the HTTP modules on the right side, trigger a followup scenario, and pass data in the headers of the request to be used in the next scenario. (while excluding variables that are not relevant for the following executions)

all of the discord modules, are simply a channel i setup as an audit log, and not relevant specifically to your question.

Hope this helps.

This has the added advantage of keeping your “variables” scoped for use case, rather than having a massive list of variables to sort through, when making edits to your scenarios.

I’ve separated the scripts. All scenarios start with the “watch update” telegram trigger, but this trigger only works in one scenario. How do I make the telegram trigger work in all scenarios? Or a solution via HTTP trigger and WEB HOOK?

1 Like

My guess on this one because make doesn’t support multiple scenarios being triggered by the same webhook for their “custom webhook solution” the same thing is being applied on an app level.

please confirm @Michaela and if this is the case, some extra documentation is probably needed to clarify what would be a webhook that starts a scenario. or a permanent (non-popup note) on the trigger module themselves in the lightbulb explanation section.

If this is the case, I have a solution incoming shortly.

You can Trigger each one of your scenarios this way, from a master “controller scenario”

And pass the variables from the telegram bot (with the advantage of only passing what is needed to keep clutter down) in the query string of the http module)
you would start each of your followup scenarios with a unique webhook using the custom webhook module. the webhook url in each of those modules, is what goes in the URL section on the http Modules.

Hope this helps!