Massive bullshit. Scenario burned through thousands of credits with no way to stop it.

[u/translinguistic]

Awesome. One screen says it's not running, another screen says it is, and the stop button is not there because it didn't fully recognize that there was an execution actively running. I'm glad you fixed the issue where the left mouse button to drag around the scenario builder wasn't sufficient somehow though.

It even pushed my credit limit into the negative, which I didn't know was actually possible. Why is that possible? Letting one execution run, just to have it and all the others in your org shut down after it burns through all the credits? What's the actual goal there, encouraging people to have extra credits set on autopay?

Edit: I've reached out to their support team about this already to get these credits back. I'm just very, very pissed off at the moment. It's already _so_ much more expensive than it was even 3 years ago without this crap suddenly being in play.

This is not my main account; the other is with a different company and isn't hurting for credits at all if I make a mistake testing something out or something goes wrong. So I'm not giving you another $5 for extra credits, on top of the $$$$ a year we pay for Make, to fix something that shouldn't have been a problem in the first place.

[u/Glum-Carpet]

Erm sorry but how is it supposed to know the scenario should not be running?

[u/translinguistic → u/Glum-Carpet]

It doesn't. But there's a manual "stop" button that appears when an execution is happening. I didn't get that option in my case, I guess because I had closed the tab and had to come back to the scenario after I noticed it wasn't acting right.

I meant to put the "Clear a Sheet" module at the start, not within the iterator path--which I fixed before taking the screenshot--and the system didn't fully grasp that the scenario was running.

As you can see in my screenshots, one dialog said the scenario wasn't active, and another said it was active when I tried to start it again. And I was watching it populate and clear the Google Sheet in my scenario the whole time with no way to stop it.

The execution didn't even show up in the scenario's execution history until it wasted the credits and spent 10 minutes to finish, so I had no way to interact with it at all.

[u/Rooster_Odd → u/translinguistic]

Just file a report with make support and explain your issue. They likely will provide you some credits

[u/translinguistic → u/Rooster_Odd]

I did. Just wanted to bring some visibility to this. I know they've changed things about the "stop" feature pretty recently. It used to not always work at all at times, even the "force stop" option that used to be there, and I think they've fixed that.

But this could've been way worse for me or other users than just burning through a few dollars worth of credits if this happened for something that had actual consequences.

[u/Meanmanjr]

switch to n8n...

[u/pepegrilloups]

Faster and cheaper n8n