Make Scenario Went Out of Control and Caused Major Damage in Systeme.io

Questions
1

:bullseye: What is your goal?

The Make system went completely out of control and caused a disaster.

It used up all my credits and created chaos inside Systeme.io.

We can clearly see that it was stuck in an infinite loop. Fortunately, I ran out of credits, which stopped it.

I’ve had this exact same scenario for over two years. It had been deactivated for the past few months.

When I reactivated it, it suddenly became like a ticking time bomb.

Before, it worked perfectly and followed the correct order of all the steps.

:thinking: What is the problem & what have you tried?

The Make system went completely out of control and caused a disaster.

1 Like
4

Hi Manu.

I’m sorry to hear of that. It’s an unusual circumstance - certainly not one I’ve heard of before!

I’d suggest your best route would be to raise this with our Helpdesk. They’ll be very interested to help find out what could have caused such an issue.

5

Hey there,

Do you mind sharing some screenshots from the history and the scenario itself? Showing how different modules are setup and what data is being processed and how?

6

Hello everyone,

Thank you for taking the time to read about my experience.

I posted on the community forum because it’s my only way to escalate this issue.

I am not looking to troubleshoot this on behalf of Make. This is not a configuration mistake — the scenario worked perfectly for several months, and nothing was changed on my side.

I am looking for an alternative solution. I’m not really interested in doing troubleshooting for Make to figure out what was changed on their end without any notice.

If the help desk is interested in fixing its bugs, they are welcome to review the operation history and the configuration of my tasks.

This situation created serious disruption for around a hundred of my clients.

Thank you to the community.

Kind regards,

Manu

7

Wait so you want to escalate the issue but you are not looking for troubleshooting?

The scenario was deactivated for the past few months and you reactivated it, but it worked perfectly for several months and nothing was changed on your side?

You are looking for a solution but you are not interested in Make figuring out what happened?

What can we as community actually do for you, then? :sweat_smile:

Sounds like a PEBKAC issue, but to be completely honest I’m just provoking to get some proof to your statements.

8

am looking for a solution, but not within Make and not using Make.

I activate this scenario depending on our needs and specific periods of the year.

The last time I activated it, yesterday, it immediately turned into a disaster.

You can close this thread.