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 minutes1)||Any|
|Runtime limits||1 hour||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 will be displayed "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 fit into the allotted time.
- Change the logic of work and optimize the code of the running script so that it has time to perform the necessary actions in the allotted time.
- If you are using a regular hosting plan, you can switch to a tariff businesshostingwhere 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 sites of the hosting account due to their lack.