Some actions (create, suspend) time out

[yggdrasil]

What timeouts does WHMCS require for PHP?

The reason I ask this is because I have it set to the default 30 seconds. My previous billing systems had no troubles with this, even for actions that took 2 minutes it always completed them fine.

WHMCS not so.

Any action that takes more than 31 seconds fails. Example is reseller accounts in cPanel where there are tons of accounts to be suspended, this can take a a few seconds and WHMCS will timeout the action. When I hit suspend/reactivate from the admin interface, sometimes it works, sometimes it takes to long and WHMCS does not updates the status, even when the action was executed in the server. It just finished but does not actually complete.

I consider this a bug.

WHMCS should do like my previous billing systems, keep the process realoding in the background regardless of how long an action takes and this should not be related to the timeout php has for loading webpages. Setting PHP higher would not solve this because if a server is slow and lets say takes over 1 minute what are you going to do? Set PHP timeouts to 100 seconds? That is just ridicolous, you are opening the whole installation to simple dos attacks as you should never let PHP have long timeouts like that. That is just horrible and no script should take longer than 30 seconds. Actions should run in batches if they take longer like my previous systems did. The ajax status was loading over 30 seconds and finally it finished fine. With WHMCS it finishes but the action actually timed out and did not executed correctly.

In the case of reactivation for resellers I had problems as it did not executed the action completely. The customer still has his account status suspended in WHMCS but in cPanel the account was reactivated. Nasty bug if you ask me.