Русский
Українська
English

Support chat

Are you a customer?

Select the type of request:

0-800-307-307 Hotline
+38 (044) 392-74-33 Kiev
+38 (057) 728-39-00 Kharkiv
+38 (056) 794-38-31 Dnipro
+38 (032) 229-58-93 Lviv
+38 (048) 738-57-70 Odessa
+38(093) 170-15-42 Life
+38 (067) 400-88-44 Kievstar
+1(888)393-24-51 USA, Toll free
+44(131)507-01-14 Great Britain
+7 (499) 348-28-61 Moscow

2.11.5. Cron limitations

The main restrictions are shown in the table.

	Regular hosting	Business hosting
Task launch frequency	No more than once every 15 minutes¹⁾	Any
Runtime limits	300 seconds (5 minutes)	4 hours
Minimum start interval	1 minute	1 minute

If the launched process does not have time to complete within the allotted time, it will be forcibly terminated by the system. Moreover, in cron log next to such a process the status “Killed».

If the execution time is insufficient, the following options are worth considering:

If the script processes a large amount of any data, you can split it into parts so that at each launch the script does not process all the data at once, but only the next part, and fits within the allotted time.
Change the logic of work and optimize the code of the running script so that it can complete the necessary actions in the allotted time.
If you are using a regular hosting plan, you can switch to a tariff business hostingwhere the execution time limit is significantly higher.

It is not possible to run tasks more than 1 time per minute using cron tools. If there is such a need, you should consider running the script in the background and setting the interval using the logic of the script itself. Please note: Running cron tasks too often can lead to high consumption server resources and errors in the operation of the hosting account sites due to their lack.

¹⁾

According to clause 5.8 terms of service.