Using Scheduled Tasks

Discover our Public Cloud offer

Shared Hosting for Everyone, imagined by developers, for developers.

Discovering the Public Cloud

Via the Advanced > Scheduled tasks menu in your administration interface, enter the commands that you wish to run, the URL that you wish to access at regular intervals and define the task repeat periods.


  • If the task is scheduled at a certain frequency but the execution of the previous task is not finished, the current one will be ignored,
  • Tasks are started during the set minute. In other words a task scheduled to start every day at 6:30 will start between 6:30:00 and 6:30:59.
  • A log is created automatically and is available from the $HOME/admin/logs/jobs/ directory. It gives you the start and end of the task.
    • An extract of these logs is presented in the administration’s interface (Logs - 📄).
  • For accounts on the Public Cloud, the consumption should remain reasonable. If the scheduled task is major processing, then reduce its frequency.

Even if it is not advisable, users of the Private Cloud) have also access to the crontab -e command. The two systems are separate.



Every ten minutes, the WordPress tool starts to run the scheduled tasks:

alwaysdata administration interface:

  • value: php $HOME/wordpress/htdocs/wp cron event run --due-now
  • frequency: second choice - Every 10 minutes

Equivalent crontab syntax:

*/10 * * * * php $HOME/wordpress/htdocs/wp cron event run --due-now


Refreshing an RSS backend with TT-rss, every day at 10:30:

alwaysdata administration interface:

  • value: php $HOME/tt-rss/update.php --feeds --quiet
  • frequency: first choice - Every day at 10:30

Equivalent crontab syntax:

30 10 * * * php $HOME/tt-rss/update.php --feeds --quiet


  • source venv/bin/activate && python is specific to Bash and can’t function. To replace per venv/bin/python.

Shortcuts with an @ - examples @hourly or @reboot - are not accepted (non-standard syntax).