Forums

Always-on task restarts after hitting CPU second soft limit?

Hi, my always-on task seems to restart itself once it hits the 2,000 CPU second soft limit I have set up on my account.

Is there any way to avoid this behaviour?

I don't mind the process slowing down, I just don't want it to restart; I have a long-running task that I need to be able to run for a long time without interruption.

Thank you!

It seems like using a console would be the solution, either that or upgrading the CPU seconds.

Why aren't always-on tasks and consoles treated in the same way?

The only way that we can change the CPU allowances for always on tasks is to change the configuration and restart them, that is why they are stopped and restarted whenever you enter or leave the tarpit.