On Cloud Platform environments, cron can be triggered using Drush in addition to using scheduled jobs.
Note
The current Drupal version requires Drush version 11 or later. Newer versions of Drush, that is, version 11 and later, must be installed via Composer. Acquia does not manage the update to the newer versions. For more information, see About Drush on Cloud Platform.
To use Drush cron, select from the following methods:
[app] is the name of your application on Cloud Platform.
[env] is your environment (typically one of dev, test, or prod).
[site_URL] is your environment’s URL (as listed on the Cloud > Domains page). If you are using Drupal multisite, your cron jobs are specific to each website in the multisite installation. Use the URL of the website in the installation you want to target.
Running Drush cron directly
You can execute alternative Drush cron commands using the following syntax:
In the preceding example, &>> /var/log/sites/${AH_SITE_NAME}/logs/$(hostname -s)/drush-cron.log logs the cron output to a drush-cron.log file in the infrastructure’s logs directory.
Cron jobs must always include a logging statement.
Triggering a cloud hook through Drush cron
For infrastructure where you want a single hook, you can also run a specific cron hook directly. The command structure will vary based on your Drupal version and module.
drush -v ev "mymodule_cron();" &>> /shared/logs/drush-cron.log
drush -v ev "mymodule_cron();" &>> /var/log/sites/${AH_SITE_NAME}/logs/$(hostname -s)/drush-cron.log
The previous commands will log output to the standard log files, ensuring log rotation and maintenance continues.
Frequently asked questions
Using Drush cron on Cloud Platform environments
On Cloud Platform environments, cron can be triggered using Drush in addition to using scheduled jobs.
Note
The current Drupal version requires Drush version 11 or later. Newer versions of Drush, that is, version 11 and later, must be installed via Composer. Acquia does not manage the update to the newer versions. For more information, see About Drush on Cloud Platform.
To use Drush cron, select from the following methods:
[app] is the name of your application on Cloud Platform.
[env] is your environment (typically one of dev, test, or prod).
[site_URL] is your environment’s URL (as listed on the Cloud > Domains page). If you are using Drupal multisite, your cron jobs are specific to each website in the multisite installation. Use the URL of the website in the installation you want to target.
Running Drush cron directly
You can execute alternative Drush cron commands using the following syntax:
In the preceding example, &>> /var/log/sites/${AH_SITE_NAME}/logs/$(hostname -s)/drush-cron.log logs the cron output to a drush-cron.log file in the infrastructure’s logs directory.
Cron jobs must always include a logging statement.
Triggering a cloud hook through Drush cron
For infrastructure where you want a single hook, you can also run a specific cron hook directly. The command structure will vary based on your Drupal version and module.
drush -v ev "mymodule_cron();" &>> /shared/logs/drush-cron.log
drush -v ev "mymodule_cron();" &>> /var/log/sites/${AH_SITE_NAME}/logs/$(hostname -s)/drush-cron.log
The previous commands will log output to the standard log files, ensuring log rotation and maintenance continues.
Frequently asked questions
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Cloud Platform