Cloud Platform

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.

Process limit for Drupal, SSHD, Scheduled Tasks, and Cloud Hooks

In Cloud Next, you cannot have more than 5000 processes for Drupal, SSHD, scheduled tasks, and Cloud Hooks. If you exceed the process limit, the system restarts the service. This interrupts running requests and results in 50x errors for Drupal.

  • If you run Shell commands from PHP in the background, such processes become defunct processes.
  • You cannot check the current number of processes on Drupal pods. However, you can view the process list on SSH pods.

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.

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.

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 host names in log paths

Scheduled jobs or cron jobs in Cloud Next must not use hardcoded host names in log paths. However, if you use /shared/logs as the directory, you can use hardcoded paths.

Limitations with scheduled jobs

When you create scheduled jobs in Cloud Next:

  • You cannot set crons at frequencies of less than 5 minutes.
  • Your cron task duration must not be more than an hour. If your cron job lasts longer than an hour, it terminates.

Limitations with Cloud Hooks

The maximum duration of Cloud Hook scripts is 1 hour. If your Cloud Hook script lasts longer than an hour, it terminates.

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 Cloud Next environments. This issue occurs for a few versions of MySQL Workbench.

If you face issues connecting to Cloud Next environments from MySQL Workbench:

  1. Locate the database credentials listed on your Databases page.
  2. Open Terminal on your local machine and 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.

Code deployment in Cloud Next 

Code deployment in Cloud Next can take a maximum of 1 hour. Environments on Cloud Next may intermittently experience code deployment times taking more than 5 minutes. Ensure that you close your SSH session before starting your code deployment. If you are in an SSH session and start code deployment, the process might fail.


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

Cloud Next uses individual mcrouter instances on each pod. This obscures information such as cache hits or misses. The underlying platform architecture might cause to misreport metrics on each request.

Therefore, the memcache_admin module does not correctly report the status of memcache instances. Cumulative statistics, available memory, and evictions are reported as zero. In addition, other statistics might be misreported.


To gather memcache statistics, run the following command in an SSH session:

acquia-memcache stats                   

This command displays statistics from the available memcache instances.

Unable to add more database connections

The following are the limits for database connections:

  • 250 connections in production environments
  • 25 connections in non-production environments

If you try to add more database connections than the specified limits, the system displays an error.