Massive bullshit. Scenario burned through thousands of credits with no way to stop it.
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.