| Cause | User interface error | CLI error |
|---|---|---|
| A job started manually by a user who is part of the organization but does not have the “execute pipelines” permission | | |
| A job started manually by a user who is no longer part of the organization | Not applicable, as the user cannot access the user interface. | |
| A job started through a webhook with a stored credential of a user who is currently part of the organization but does not have the “execute pipelines” permission. | Not applicable, as the job cannot start. | |
| A job started through a webhook with a stored credential of a user who is no longer part of the organization | Not applicable, as the job cannot start. | |
Pipelines executes jobs using the credentials of the user who first executes a Pipelines build. If this user leaves your organization, or the user’s credentials are revoked, you may be able to start a manual build, but automated builds may fail with errors like the following:
The application you are trying to access does not exist, or you do not have permission to access it.You can manually reset the credentials for the application.
Any user with the Execute Pipelines permission can reconfigure automated builds. For 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.
Fri Jun 20 2025 06:41:52 GMT+0000 (Coordinated Universal Time)