This section provides answers to frequently asked questions about Autopilot.
Yes. Access to Autopilot is account-based and individual sites in that account can turn Autopilot on and off as desired. See Enable Autopilot.
Yes. Configure Autopilot activity digests and notifications in your Personal Workspace settings Notifications tab.
Autopilot supports all versions of Drupal, as follows:
Drupal sites that use Integrated Composer are compatible with Autopilot.
Sites on Drupal 7 or 8 that are not using Integrated Composer, must use Drush 8 to be compatible with Autopilot.
Refer to the Autopilot Terminus plugin documentation for information on supported actions.
Your updates will appear under Ready to Deploy if the updates pass VRT. Your updates will appear under Needs Review if the updates fail VRT. The updates must be deployed manually from either location. Refer to Update Destination & Frequency for more information.
Yes. You must select the Do Not Deploy option under Destination & Frequency. This stops updates at the Autopilot Multidev. Your updates will be tested but not deployed to any environment if you select this option. Your updates will appear under Ready to Deploy if the updates pass VRT. Your updates will appear under Needs Review if the updates fail VRT. The updates must be deployed manually from either location.
You can specify the environments to which Autopilot deploys. See the configuration options.
Autopilot tests updates against a Multidev cloned from the current Dev environment by default. Opt into the Sync Environment feature in the site's Configuration tab to sync your Live environment before Autopilot checks for updates.
No. If you encounter any issues about Multidev limits, contact Support.
Not yet. Currently, Autopilot only supports tests on anonymous access versions of pages. Support for authenticated (logged-in user) page tests is planned for a future release.
Autopilot only checks for changes and updates to modules, themes, and core. You should take time to carefully review and test changes that fall outside of Autopilot's scope, including:
Other backend changes
Yes. Depending on your Account, Autopilot can be set for up to 25 pages on each site. It will check for updates once a week, and can also be run on demand.
Yes, Autopilot is compatible with premium and paid WordPress plugins. Refer to Configure Autopilot for Premium and Paid Plugins for more information.