🎥 Recording & Recap: Recent Releases and Community Roadmap Preview

[Natalija.Nat]

Hey Makers

A huge thank-you to everyone who joined our Community Live Session: Recent Releases and Community Roadmap Preview!

It was amazing to see so many of you there. For those who couldn’t make it, or if you’d like to revisit the sneak-peak of what’s coming at Make, we’ve got everything you need right here.

Full recording

Catch the full session with our Product Team Leaders, here:

Q&A from the session

Q1: Should we expected the “cost” in credit for the code module to changes?

A: We don’t expect changes in pricing of Make Code. The pricing is 2 credits per 1 sec of code execution time for most of paid plans

Q2: How is this new code module billed? I mean, I suppose it is not the same running a simple code rather than a complex one right? Also, is it possible to install new python libraries in case they are not available in the main module?

A: The billing is based on the execution time. Every second equals to 2 credits. The environment has some libraries preinstalled. Check out https://apps.make.com/code and if you need any other library, we currently provide this option only to enterprise customers.

Q3: Hi, do you have some free courses/credits for university students? How can they practice it for their assignments?

A: We have our academy free for everyone to learn the power of Make. Please reach out to Jana, Jana (j.breska@make.com) who will be able to help you specifically with that

Q4: This is a great new capability. . .when will it be available in OEM? (scenarios customized run name)

A: Working on it! We believe in the coming weeks.

Q5: What is the maximum payload that can be passed to a sub-scenario ?

A: The limit is ~ 5 MB. If a user wants to pass a huge payload (for example, Zoom recording), we recommend to pass only the link to the recording and let the subscenario download the binary data.

Q6: Do the replay runs cost credits / operations?

A: Yes, the first module is for free as we replace it with old data. The rest is as usual.

Q7: Can you add external libraries?

A: Yes! This capability is available on our enterprise plan https://apps.make.com/code#_lA2o

Q8: Will you share this scenario in MAKE scenario platform ?

A: Sure! Here it is: we.make.com/public/shared-scenario/uGscdIJfU8o/ai-powered-community-feedback-triage

Q9: After using the shared scenario, do we need to set up the configuration again just like JSON sharing? Or would the configurations be preserved?

A: The thing the recipient needs to configure are connections and connection specific parameters - eg. which spreadsheet etc. Other mapping is preserved

Q10: If I understand is the benefit of the “replay scenario runs” intended to prevent loss of data that failed earlier?

A: Yes, run replay is intended to prevent the loss of data from errored runs, but I recommend using incomplete executions (runs from the point of failure) as the primary solution and run replay (runs from the trigger) as the secondary solution.Three use cases for the run replay:

1. Recover from errors: you can replay runs to resolve logical errors (for example, faulty filters, incorrect data mapping, missing modules) and ensure the entire scenario is processed successfully from start to finish.
2. Test and debug scenarios: as you progressively build and test scenarios, you can run the scenario with existing data to reuse trigger data from past scenario runs.
3. Backfill data: you can replay the run to retroactively populate data in third-party systems when you forgot to send data to a system when building a scenario, or when you accidentally deleted data from the system.

Q11: For sharing scenarios, is the recipient able to “save as new” and modify to fit their specific needs?

A: Yes, it gets cloned into the recipient’s org and they can do whatever they need

Q12: Will it also be possible to have a specific sub-1-minute interval of picking up input data? => 0.1 Runs/Minute => 1 Run each 10 seconds, instead of 6 Runs/Minute where they run in parallel.
Problem some services rate limit by 1 request all 10 seconds - atm the least

A: We haven’t considered this so far, thanks for the input. At the moment, you can play around with rate limits in combination with sequential processing and sleep module

Q13: If the scenario iterates on an array does the replay resets the index to 1 or it keeps the last one and goes form there

A: Replay starts from the very beginning of the scenario - so to answer clearly, it starts from the first item on the iterator

Q14:A scenario support high amount of simultaneous requests ? Is that what you said ?

A: Yes, scenarios are executed in parallel in default.

Q15: So what happens to requests that exceed the rate limit?

A: They stay in the webhook queue until their time comes

Q16: Can you please share the link where I sign up for MAIA Beta please?

A: Of course Join the Closed Beta - Make AI Agents & Make Maia.

Q17: Can we expect in-scenario agent prompting to find a specific error or behavior?

A: This is something our team is considering. Read more about it over here: make.com/en/blog/make-maia-no-code

Q18: Does the ‘Maximum runs to start per minute’ setting trigger separate runs each time, or does it keep the scenario running continuously? And could this cause us to hit the per-scenario execution time limit?

It separates runs each time - so no worry regarding per-scenario execution time limit.

Q19: Does the Merge module kind act like using set variable , get variable and building objects for sorting data ??

A: The Merge module in this upcoming release is designed to work exclusively with the new If-Else module. Unlike the variable workaround, where you manually build objects to capture data from various paths, the Merge module is designed for mutually exclusive paths where
only one branch ever executes. You will be able to specify exactly what the output is in the Merge module settings based on which branch was executed.
Because the input comes from only one source at a time, this version does not function as a tool for sorting or combining data from parallel branches. However, we aim to support merging inputs from multiple branches in future iterations.

Q20: And free right? No cost using that module right?

A: Yes, Run Name is free for use! Abuse it as you please You can use it even multiple times within one scenario to update the name as the run progresses
If Else & Merge it will be also for free, router also doesn’t cost anything.

Q21: Please tell when the new tools “if/else” and “merge” will be implemented?.

A: You can expect Open Beta early next year. The general availability should follow soon after as the closed beta is planned to be stable.

Q22: When the human-in-the loop module is coming?

A: We’re making the necessary architectural steps to make it happen as we speak, but it’s gonna take us a couple of months to bring it to you! Stay tuned.

---

We’d love to hear your thoughts

What was your biggest takeaway from the session? Share your thoughts or ask follow-up questions below.

[Henk-Operative]

Looking forward so much to the if/else and merge modules!