Are you using Make.com in production?

Off-Topic
1

Hi all,

I’m pretty new to Make.com. I love the concept and enjoy quite a bit of the UI, although I feel a lot of progress could still be made.

I work with entrepreneurs and other leaders on using AI to improve their own leadership. One of the subjects is, of course, building automations and talking to for instance the OpenAI API. So far, so good.

After building out a couple of very promising scenarios for my own use, I’m now in the situation where quite a few of my scenarios encountered this: ‘Unexpected internal error was caught. Contact the support.’

I then had to wrestle myself through the support ticketing system that Make uses, asking me to fill out non-existing answers to irrelevant questions.

They replied with a pretty generic ‘I am sorry for any inconvenience. This issue was already fixed and all of your scenarios should work already just fine. In case some of them are not running please turn then On again.’

In the meantime, a couple of days later, I still feel that my scenarios are not running as well as before. At least one of them has 211 incompleted executions, and no clear button, instructions or other path to clear up that backlog.

The main dashboard doesn’t give me a clear picture of which scenarios have encountered problems, or still have some issues or a backlog.

This entire situation seems to me to be pretty murky.

So, there’s my question: is somebody running Make.com in real production environments?

Was the internal error of last week an outlier, that never happened before?

Am I missing something, and should I just find one other page that is really meant to help troubleshoot situations like this?

Or should I refrain from advising my readers (25k+) and clients to use Make.com for serious production work for now?

I could still see a case where it might be very useful for prototyping. But I cannot in good conscience advise people to build their processes on Make, if they’re bound to encounter similar confusing, show-stopping situations like I’m in right now.

Thanks for sharing any insights!
Tom

2

Welcome to the Make community!

While I’m currently using Make only for personal use, I’m sure there are others using it in their production environment.

It really depends on the specific issues your scenario is having.

If you can’t share/discuss the scenarios with us here, then the only way is to either contact support or hire a professional to look at it for you.

For complex technical issues or bugs like this, directly contacting support can often lead to a faster resolution. They have access to your specific account details, scenario and scenario logs, server-side logs, and internal tools and resources, which allows them to investigate more thoroughly than what you have access to. Additionally, sharing sensitive information about your situation might not be suitable for an open forum discussion.

You can open a new ticket, or if you are unable to login for some reason, you also can reach support using the contact form on the website.

samliew – request private consultation

Join the unofficial Make Discord server to chat with us!

2 Likes
3

Thanks a lot for your response, @samliew - and for your warm welcome. I appreciate it.

As far as I can see, my scenarios have no issues. Apart from the fact that they don’t seem to be running and doing what I built them to do.

For instance, I have a scenario that monitors an RRS feed. It shows an error for June 18th, which is the exact date when Make ran into problems. See https://status.make.com/. Their report of this incident mentions: ‘This incident has been resolved.’

My RRS-monitor scenario was deactivated by Make, according to the HISTORY panel. And then it ran 2 more times on June 18th, and 2 more times on June 19th. That’s it.

The settings for this scenario say that it has to run Every 1 hour. The scheduling toggle is set to ON. And when I press the RUN button myself, it will dutifully go out, check the RRS feed and execute the rest of the scenario.

After doing that 3 times, the HISTORY panel now shows 3 more runs for today. Makes sense.

What doesn’t make sense, at least not to me, is that it isn’t running every hour. It doesn’t tell me why it isn’t running every hour. There’s no warning indicator in the list of scenario’s that it isn’t running every hour. There is no notification that it isn’t running every hour.

I have at least 4 or 5 more scenario’s with similar problems. And I don’t fancy having to go into each scenario every hour myself, to press the RUN button.

But, to be clear, my question here is not: how do I fix this problem in my scenario?

My question is, if problems like this occur, with no indication, no warning, no easy way to solve them, how can I advise people to use Make in production?

Thanks :blush:
Tom

4

I still cannot believe this, but I think the support engineer from Make just suggested that I have to go into each Incomplete Execution by hand, and press the Run Once button.

Isn’t this meant to be a platform for automations?

I love the Indy hacker world, and the enthusiasm and all the examples on Tiktok.

But… how can you in good faith ask clients to pay for a platform like this, if it has no good, automated systems for monitoring and rapidly solving issues like this?

5

An incomplete execution happens when some sort of error occurs that is not handled by an error handler. And yes you do have to rerun most incomplete executions by hand. You can add an error handler to attempt to retry errors that occur, but first it’s important to figure out why incomplete executions are happening in the first place.

6

Hey @alex.newpath - there was no error in my scenario.

Instead, Make had an internal error, that they reported on their status page:

…
Jun 18, 2024

Scenario executions delayed in EU2 and US1

Resolved - This incident has been resolved.
Jun 18, 19:35 CEST

Update - We have identified set of scenarios which got disabled due to this incident and we will proceed with activating them again.
Jun 18, 19:21 CEST

Monitoring - We have applied a fix and the situation is stable. We will keep monitoring the situation.
Jun 18, 18:09 CEST

Identified - We have identified a root cause and working on a fix.
Jun 18, 17:56 CEST

Investigating - We are experiencing delays in scenario execution in EU2 and US1 zones. We also observe issues with some scheduled scenarios (mainly with Gmail or RSS triggers).
Jun 18, 17:56 CEST
…

So, as far as I can see, there’s nothing much for me to investigate, apart from the question if Make is ready for production.

Right now, I don’t see how I can in good faith recommend an automation platform to my clients, where if there is a problem, they have to potentially restart hundreds of jobs by hand.

And there isn’t even an indication in their main dashboard that these problem exist, so they have to go into each and every scenario themselves to see if there is a backlog of missed executions.

I may be too naive, but I really can’t see how all these automation agencies on Tiktok are telling their clients,

'Well, you know, you pay us to build scenarios on Make, and you also pay the Make platform to run them, but you know, they just had this internal error last week, and now we need you to go in and manually restart all the missed executions. Or we can do that for you and charge you x amount of dollars per hour."

How on earth?

Tom

2 Likes