Hey @AleDaldox,
So how this setting works is that it will cut a simulation if it runs for longer than you specified there. That’s very useful when you have new simulations that you don’t know for how long they will run so that you can keep your core hours safe. What we typically do is specify a number that is way above the time we expect the simulation to be solved in so that the platform doesn’t cut them short and we can get results.
What’s happening right now is that because you’re on the professional account trial you get 200 core hours. Using 32 cores that means that you have a maximum runtime of 22,500 s (way below the value in the tutorial). This can be solved in two ways:
- You can change the maximum runtime to around 8,000 s (a bit more than two hours) which should still keep your simulation safe (as it’s supposed to be done in less than 2 hours)
- We can change your account to a free community plan where all your projects will be public, but you get 3,000 core hours (which means you could use a maximum runtime of up to 337,500 s)
Please let us know if you would like to change your account or if you go with the first alternative 
Hope this helped!
Best,
Diego