Error | Description |
---|---|
[RuntimeException] No credentials found. Configure the client. | You have not yet signed in to Pipelines. For information about obtaining an API token to use with the pipelines configure command, see Configuring the client (authentication) You may find it easier to connect using the Cloud Platform Pipelines user interface instead of the command line. |
[RuntimeException] API key not found | The Cloud Platform API key (the n3_key line in ~/.acquia/pipelines/credentials ) that you provided to the pipelines configure command is not valid. For information about obtaining an API token to use with the pipelines configure command, see Installing the Pipelines client. |
[RuntimeException] Signature not valid | The Cloud Platform API key secret (the n3_secret line in ~/.acquia/pipelines/credentials ) that you provided to the pipelines configure command is not valid. For information about obtaining an API token to use with the pipelines configure command, see Installing the Pipelines client. |
[RuntimeException] The feature you are trying to access is not enabled on this application. | This Acquia subscription is not set up to use Pipelines. To have this subscription be enabled, contact Acquia Support. |
Request failed with status code 403: Forbidden | You do not have the Execute Pipelines permission for the Cloud Platform application that you’re working with. Contact an Administrator or Team lead for this application to provide you that permission, which by default, is granted to users who have been assigned the Team lead or Senior Developer role, but not to users with the Developer role. For more information, see Working with roles and permissions. |
System failure | System failure errors may occur if the Pipelines job exceeds maximum memory or time limits. You should refactor your tasks to operate within container limits. If you need additional assistance, contact Acquia Support. |
After you fix any detected issues with any pipeline jobs, run the start
command again to restart the build.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Thu May 08 2025 09:24:23 GMT+0000 (Coordinated Universal Time)