--- title: "Known issues in Code Studio" date: "2024-02-14T06:18:38+00:00" summary: "Explore known issues in Code Studio, including security job execution, PHP version conflicts, and deployment challenges for Drupal developers." image: type: "page" url: "/acquia-cloud-platform/add-ons/code-studio/known-issues-code-studio" id: "d2add43b-6419-4fa6-bf34-8bc68e2d8545" --- Table of contents will be added. This page describes known issues in Code Studio. For issues with Cloud Platform CD, see [Known issues in Cloud Platform CD](/acquia-cloud-platform/features/cd/known-issues). **Security job execution for ACQUIA\_JOBS\_TEST\_DRUPAL disabled** ------------------------------------------------------------------ When the environment variable named `ACQUIA_JOBS_TEST_DRUPAL` is set to `false`, specific security-related jobs continue to execute in the pipeline. These jobs include: * semgrep-sast * secret\_detection * sobelow-sast No environment variable exists to independently disable each of these jobs. _Workaround:_ To prevent these jobs from running, add the following definitions to override the configuration in the`.gitlab-ci.yml` file: semgrep-sast: rules: - when: never sobelow-sast: rules: - when: never secret_detection: rules: - when: never This will ensure that semgrep-sast, sobelow-sast, and secret\_detection do not run in the pipeline. If your project does not contain a .gitlab-ci.yml file, refer to the documentation for instructions on [how to use a custom .gitlab.yml file](https://docs.acquia.com/acquia-cloud-platform/add-ons/code-studio/customizing-default-code-studio-pipeline?previewMode=current#section-using-a-custom-gitlab-ciyml-file).  New environments provision with Cloud Platform default PHP version ------------------------------------------------------------------ If a new Cloud Platform environment is provisioned by a CI/CD process, such as [Acquia Pipelines](/acquia-cloud-platform/features/pipelines) or [Acquia Code Studio](../code-studio.html), the new environment is provisioned with the default Cloud Platform PHP version. The new environment does not inherit the PHP settings from the source environment or CI/CD build. For more information on the default PHP version, see [default Cloud Platform PHP version](/acquia-cloud-platform/manage-apps/php#cloud-php-version-used). _Workaround_: You must set your desired PHP version for the new environment. You can configure the PHP version through the [Cloud Platform user interface](/acquia-cloud-platform/manage-apps/php) or the command line. * **Cloud Platform user interface**: Modify the PHP version for your application at the environment level using the [configuration settings](/acquia-cloud-platform/manage-apps/php) after the new environment is deployed. * **Command line**: Change the PHP version with the following [Acquia CLI](/acquia-cloud-platform/add-ons/acquia-cli/overview "Overview") command: acli app:task-wait "$(acli api:environments:update $TARGET_ENV_ID --lang_version=8.1)" Note If your Drupal application contains deprecated code, changing the PHP version after deployment might cause initial failure notices. The Test Drupal stage fails due to incompatible PHP version ----------------------------------------------------------- The [Test Drupal stage](/acquia-cloud-platform/add-ons/code-studio/customizing/autodevops-jobs#section-test-drupal-stage) fails to complete execution if the PHP version in Code Studio does not match with the version of the PHP dependency specified in the `composer.json` file. _Workaround_: To satisfy the version requirement specified in the `composer.json` file, you must change the PHP version in Code Studio. For more information, see [Modifying environment variables](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/default-code-studio-pipeline/environment-variables#section-modifying-environment-variables). Ensure that you do not select the **Protect variable** checkbox. Runner pod returns a timeout error ---------------------------------- The [Build Drupal stage](/acquia-cloud-platform/add-ons/code-studio/customizing/autodevops-jobs#section-build-drupal-stage) fails to complete execution while waiting for the runner pod to start. This is related to an [open issue on GitLab](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28747). Unspecified error ----------------- Pipeline fails due to an unspecified error. _Workaround_: Clear the runner caches. Unable to transfer project ownership ------------------------------------ You cannot fully transfer the ownership of a Code Studio project through Cloud UI. You can add a second owner if more than one Code Studio seat exists. The second owner can neither change the role of the original owner nor revoke the seat of the original owner. To transfer project ownership, contact your Technical Account Manager (TAM) or [Acquia Support](/service-offerings/support#contact-acquia-support). Deploy  job fail for Federated Authentication projects ------------------------------------------------------ The [Deploy](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/drupal-auto-devops/autodevops-jobs#section-deploy-drupal-stage) job fails with the following error: ``Run `acli login` to authenticate via API token and then try again.`` For information about the known issue related to Federated Authentication, see [Federated Authentication requires a workaround](/acquia-cloud-platform/add-ons/acquia-cli/known-issues#federated-authentication-does-not-work). _Workaround_: Add the `AH_ORGANIZATION_UUID` environment variable to your Code Studio project through the CI/CD variables UI. If the variable is added to the `.gitlab-ci.yml` file, it might not work as expected. For more information, see [Adding environment variables](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/default-code-studio-pipeline/environment-variables#section-adding-environment-variables). Note To find your organization UUID: 1. Access [Acquia Cloud organizations](https://cloud.acquia.com/a/organizations). 2. Select your organization. 3. Retrieve the organization UUID from the URL: [https://cloud.acquia.com/a/organizations/](https://cloud.acquia.com/a/organizations/)****. The Code Studio branch URL in the Cloud Platform user interface is incorrect ---------------------------------------------------------------------------- The Code Studio branch URL that appears next to each environment in the Cloud Platform user interface contains `-codestudio-build` as an additional string. Therefore, when you click the URL, the system displays a 404 error. Newly created on-demand environments do not sync with Cloud Platform databases ------------------------------------------------------------------------------ Newly created on-demand environments must sync with Cloud Platform databases if you set the `ACQUIA_CLOUD_SOURCE_ENVIRONMENT_ID` environment variable. However, Code Studio creates an on-demand environment with a new database instead of using the copied Cloud Platform database. Drupal artifact does not include front-end build assets ------------------------------------------------------- Code Studio runs `acli push:artifact` to deploy build artifacts. The artifact does not include front-end build assets because the `.gitignore` file ignores them. _Workaround_: Complete the following steps: 1. To override the `.gitignore` file and commit the files: 1. In the `composer.json` file, locate the `extra` key. 2. In the `installer-paths` key, add an entry with the path to the files that are not present in the artifact. 2. Add `post-install-cmd` to your `composer.json` file. For more information, see [Building front-end dependencies for Drupal](/node/56077#section-building-front-end-dependencies). 3. To update your `composer.lock` file with the preceding changes, run `composer update --lock`. [Unable to configure merge request approval rules](#id12) --------------------------------------------------------- You cannot configure merge request approval rules in your Code Studio account. Code Studio creates CDEs for all branches ----------------------------------------- Code Studio creates CDEs on non-protected branches and tags even if the `ACQUIA_JOBS_CREATE_CDE` environment variable is configured only for protected branches and tags. CDE creation fails when the PHP version is set to 8.3 ----------------------------------------------------- When the PHP version of a Code Studio project is set to 8.3, the [Continuous Delivery Environment (CDE)](/acquia-cloud-platform/cloud-platform-cd "https://docs.acquia.com/acquia-cloud-platform/features/cd") creation fails during the [Deploy Drupal stage](/node/56075/#section-deploy-drupal-stage "https://docs.acquia.com/acquia-cloud-platform/add-ons/code-studio/customizing/autodevops-jobs.html#deploy-drupal-stage") because Cloud Platform currently does not support PHP 8.3. _Workaround_:  Add the `ACQUIA_JOBS_CREATE_CDE` [environment variable](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/default-code-studio-pipeline/environment-variables#section-using-environment-variables-to-enable-or-disable-a-cicd-job "https://docs.acquia.com/acquia-cloud-platform/add-ons/code-studio/customizing/default-code-studio-pipeline#section-environment-variables-to-enable-or-disable-a-cicd-job") and set it to `false` so that Code Studio skips CDE creation.