Known issues in Cloud Next

Cloud Platform versions: Cloud Platform documentation refers to both the Cloud Classic and Cloud Next versions of this product, unless otherwise noted.

This page describes the known issues in Cloud Next. For known issues that apply to Cloud Platform generally and Cloud Classic specifically, see Known issues in Cloud Platform and Known issues in Cloud Classic respectively.


In addition to applying the workarounds mentioned on this page as applicable, you must make the additional changes for Cloud Next readiness.

Copy or import of databases fails

If the definition of a VIEW contains the database name in its defining query, you cannot copy or import databases.


Edit the VIEW and remove all occurrences of the database name from its defining SQL query.

For example,

mysql> show databases;
| Database                         |
| information_schema               |
| db-name-printed-here             |
2 rows in set (0.02 sec)
SHOW CREATE VIEW some-view-name;
CREATE VIEW `some-view-name` AS select `db-name-printed-here`.`uid` AS `uid` FROM `db-name-printed-here`.`fields`

In this example, you must update the VIEW definition to remove the occurrences of the database name, db-name-printed-here.

Interruption in web requests taking longer than 10 minutes

In Cloud Next applications, web requests that take longer than 10 minutes might be interrupted by routine platform maintenance activities.

Two daily backups

The Cloud Platform user interface may occasionally display two daily backup tasks for the same day, indicating the backups taken at different times of the day.

Unable to copy files between environments

The system might display the following error when you attempt to copy files between environments:

rsync: change_dir "/mnt/source/mnt/data/[UUID]-real-shared/sites/[SITENAME]/files" failed: No such file or directory (2)

Until Acquia provides a resolution, create a Support ticket for assistance with copying files.

“End of script output before headers” error occurs if the HTTP response header exceeds 8 KB

Cloud Next introduces a limit of 8 KB to HTTP response headers. When using HTTP headers, ensure that the header size does not exceed this limit. For example, this limit might be triggered when you use:

  • Acquia Purge module that is configured to output debug headers

  • Security Kit (seckit) module that is configured to output X-Content-Security-Policy headers

File copy operation takes longer in Cloud Next compared to Cloud Classic

The file copy operation in Cloud Next takes longer as compared to Cloud Classic. This occurs because the files are first copied from the production environment to an intermediate ODE environment, and then to a migration environment. After the copy operation is complete, the system deletes the ODE environment, thereby keeping only the migration environment. This additional step in the migration process consumes more time.

Cloud hooks are not executed

When you copy files or databases from a Cloud Next environment to a Cloud Classic environment, cloud hooks are not executed.

Until Acquia provides a resolution, contact Acquia Support for assistance with copying files.

Change in mod_headers behavior in Cloud Next

In Cloud Classic, mod_headers directives in the .htaccess file are ignored for PHP and Drupal requests, and are only applied to static files. However, in Cloud Next, mod_headers directives in the .htaccess file are applied. This might result in unexpected or unwanted changes in application behavior. Acquia recommends that you review your .htaccess file for mod_headers usage.

Static IPs not supported for Log Forwarding

Currently, Cloud Next does not support sending logs from static IPs.

MySQL 5.7 features incompatibilities on Cloud Next

Cloud Next leverages AWS Aurora MySQL. A few of the MySQL 5.7 features are not supported on Cloud Next. For more information, see list of unsupported MySQL 5.7 features.

Scheduled jobs must not use hardcoded log paths

Scheduled jobs or cron jobs on Cloud Next must not use hardcoded log paths.

Issues connecting to Cloud Next environments with locally-installed MySQL Workbench

If you have MySQL Workbench installed locally, you might not be able to connect to environments on Cloud Next. This issue occurs for a few versions of MySQL Workbench.

However, you are not impacted if you are running Sequel Pro locally.

If you face issues connecting to Cloud Next environments from MySQL Workbench, do the following:

  1. Locate the database credentials listed on your Databases page.

  2. In a terminal in your PC, run:

    {ssh -L $LOCAL_PORT:$DB_HOST:3306 $SSH_STRING}


    • LOCAL_PORT is the port to which Workbench must connect when using localhost.

    • DB_HOST is the hostname obtained from the Cloud Platform user interface.

    • SSH_STRING is the full connection string from the Cloud Platform user interface. For example, user@something.

Long code deployment times

Environments on Cloud Next may intermittently experience code deployment times taking more than five minutes.

Unable to increase PHP file upload size

Currently, you cannot increase the PHP file upload size values beyond the limits available in the Cloud Platform user interface. The maximum size for Cloud Next is 256 MB.

Workarounds: You can use either of the following workarounds:

  • Use the contributed module, DropzoneJS, and specifically the chunked uploads patch in DropzoneJS. For more information, see Use contributed modules for file upload handling.

  • Upload a small dummy file of the next version of your software through the Drupal user interface. After that, you can access the Acquia Cloud service through SSH or SFTP, push the actual file, replacing the original dummy file. This process enables you to reference the file in Drupal and utilize it visually according to your preferences in Drupal.

memcache_admin incompatibility

The memcache_admin module does not correctly report the status of memcache instances. Cumulative statistics, available memory, and evictions are reported as zero.