Platform Ideas and Improvements

It would be extremely helpful to allow multiple error handlers to be combined on the same module. For example, I would like to configure a module to: Retry a failed operation up to 3x Then Skip that specific bundle if it continues to fail after those 3 retries This would allow the failed submission a few opportunities to succeed, but not let that one persistent failure hold up the rest of the scenario.

Currently merlin opens a tiny window that works but doesn't allow for viewing more than a few lines - nowhere enough to see what is being written. Having a pop out feature or at least a way to expand the window would make it much simpler to converse. I specifically was using the version on page https://www.make.com/en/get-help

I'm having a difficult time understanding how this is still not an available feature. When users are trying to figure out what is using the most credits, they have to scroll through an endless list of transactions, maybe copy and paste into a spreadsheet to get a summary? Why can't Make easily show us which scenarios are using the most credits? I can't understand why that wasn't part of the initial credit history feature. How many people actually care about how many credits a scenario used on one run last Tuesday vs how many credits a scenario used in a week, month, or year? It seems obvious to me, but I could be missing something.

Would it be possible to allow two users to edit the same scenario simultaneously, with real-time collaboration features such as seeing each other's cursor movements and live updates as changes are made?

Great work with the new AI, really. It's good to see, and it's been such a helpful feature. I think it would be really great to access it from a central place where one can use it to work across multiple scenarios. On the grid, maybe?

I'm having an issue where one (or several) scenarios are crushing my operations and I don't know which one(s) they are. I've had to add $40 extra TODAY to keep my scenarios live. This seems like a system flaw...If you're able to track my total operation count, I should be able to see what scenarios are creating those operations by date filter. If this sort of filter existed, I'd be able to click on my daily operation number (in the graph) and then be brought to a page where the individual scenarios that made up those total operations (for the date I clicked on) are displayed (sorting by the most used at the top).

Able to import and export data structures. Ideally any data structure used in a scenario should also export in a Blueprint which it doesn't at the moment.

Product ID in shopify is a hidden data. It is not easy to work with. Searching Product and Get Product should allow SKU data input.

Unfortunately the Parse CSV module doesn't use the CSV headers even if you activate the option ‘CSV contains headers’. For further details, please see the following thread: https://community.make.com/t/csv-headers-are-gone-after-parsing-even-with-headers-on/4220

Prevent a developer from using a connection that gives access to sensitive data. If the connection is to be used again (on an edit or a new scenario), it should request credentials again. For instance, the use case is the following: If a specific Google Account connection gives access to sensitive HR data, then we would like only authorized Integromat developers to use this app in new or existing scenarios. They would have to authenticate each time they'd like to modify the module in the scenario, or use a new module with this connection.