Troubleshooting

Common issues you may hit anywhere in DevOps Pipeline, grouped by where they happen in the workflow. If your issue isn't listed, contact your Project Admin or Organization Admin.

Projects and permissions

Issue	Cause	Resolution
A Project is missing from the list	Access has not been granted.	Contact the Organization Admin.
The Create project button is not visible	You lack permission to create Projects.	Contact your Administrator.
Cannot edit a Project	You lack sufficient edit permissions.	Contact your Administrator.
A Project does not appear in search results	The keyword is incorrect, or you lack access.	Double-check your search keyword.
Cannot open a Project	Your access has been revoked.	Contact your Administrator.

See Project management.

Creating and saving a pipeline

Issue	Cause	Resolution
Can't create a Pipeline	You don't have sufficient permissions, or the Project isn't configured correctly.	Contact your Project Admin.
Repository doesn't appear when adding a source	The Git Connection hasn't been configured, or you don't have access to the repository.	Review your Connection settings.
Can't save the Pipeline	The Pipeline doesn't meet the minimum requirements — no Pipeline Source, Stage, or Job added.	Add a Pipeline Source, at least one Stage, and at least one Job.

Frequently asked

• Can I create multiple Jobs in a single Stage? Yes — a single Stage can contain multiple Jobs, depending on your CI/CD workflow.
• Can I add Stages after the Pipeline is created? Yes — a Pipeline can be edited and extended with new Stages at any time.

See Create and configure a pipeline.

Triggers

Issue	Cause	Resolution
Pipeline does not run automatically	Auto Trigger is not enabled.	Check the Trigger Configuration.
Code is pushed but the Pipeline does not run	The branch does not match the Branch Filter.	Check the Branch Filter.
GitLab reports a Webhook error	The URL or Token is incorrect.	Check the Webhook Configuration.
Trigger stops working after a Token regeneration	GitLab is still using the old Token.	Update the new Token in GitLab.
Webhook information is not shown	The Trigger is not enabled.	Enable Auto Trigger first.

See Configure triggers.

Deployment

Issue	Cause	Resolution
Cannot save Deployment — Job Name missing	The Job Name field is empty.	Enter a valid Job Name.
Cannot save Deployment — no Environment	No Environment was selected.	Select an Environment.
Cannot save Deployment — no Deployment Strategy	No Deployment Strategy was selected.	Select a Deployment Strategy.
Cannot save Deployment — no Chart Version	No Chart Version was selected.	Select a Chart Version.
Invalid YAML format	The Values YAML has a syntax error.	Review and correct the YAML.
ConfigMap Name is required	The ConfigMap name wasn't entered.	Enter a ConfigMap name.
Duplicate ConfigMap Key	A Key is duplicated in the ConfigMap.	Use a different Key.
Secret Name is required	The Secret name wasn't entered.	Enter a Secret name.
Duplicate Secret Key	A Key is duplicated in the Secret.	Use a different Key.
Environment not available	The Environment hasn't been configured.	Configure the Environment first.
No edit permission	Insufficient permissions.	Contact your Project Admin.
Namespace not found	The Namespace doesn't exist in the Environment.	Check the Environment settings.
Image Version not visible	No image has been built or pushed.	Check the Build Pipeline.
Auto Deploy not running	Deployment Trigger isn't set to Auto.	Check the Deployment Configuration.
Auto Deploy not running	The Pipeline completed with a Failed status.	Check the Pipeline Run.
Deployment Failed	The Deployment Configuration is invalid.	Review the Deployment Configuration.
Deployment Failed	The Environment is unavailable.	Check the Cluster and Namespace.

See Deploy config & deploy application.

Kubectl jobs

Issue	Cause	Resolution
"No Git credential configured" when selecting Git repository	No Git connection has been added to the Project yet.	Add a Git connection under Credentials first.
Job fails at the dry-run step	The manifest content has an error.	Review and correct the manifest — dry-run catches errors before the real apply runs, so the cluster is unaffected.
Job saved with "Add job" doesn't persist after leaving the page	The Pipeline itself wasn't saved.	Click Save Pipeline — "Add job" only saves the Job within the current editing session.
Arguments field is missing for a non-Apply Operation	The wrong Operation is selected, or it was just changed.	Confirm the selected Operation — each has its own Configuration, and switching Operation clears the previous fields.

See Add a Kubectl job.

Running and monitoring

Issue	Cause	Resolution
Pipeline doesn't run after clicking Run Pipeline	You don't have permission to run it, the Pipeline isn't fully configured, or a temporary system error occurred.	Check your access permissions, and contact the Project Admin if needed.
Pipeline Run failed	The build failed, a test failed, the deployment failed, or the target environment is unavailable.	Check the Stage and Job Logs to identify the cause.

Frequently asked

• Can I run multiple Pipeline Runs at the same time? Yes — each click of Run Pipeline creates a new, independently managed Pipeline Run.
• Can I stop a Pipeline that has already completed? No — Stop Pipeline is only available while the Pipeline is in the Running state.
• After stopping a Pipeline, can I resume from where it stopped? No — you need to create a new Pipeline Run.

See Run and monitor a pipeline.

History and logs

Issue	Cause	Resolution
"Run history" tab not visible or not clickable	No Pipeline view permission.	Contact Admin to request access.
"Run history" option is greyed out in the dropdown	The Pipeline has never been run.	Run the Pipeline at least once first.
No results after searching	The keyword is incorrect or has fewer than 2 characters.	Enter at least 2 characters, and verify the Run ID or actor name.
"Re-run" button is disabled	The original run is still Processing.	Wait for the current run to finish, or stop it first.
Re-run returns "Config no longer valid"	The original run's config has been deleted.	Create a new run from the current Pipeline configuration.
"Stop" button not visible	The run is not in a Processing state.	Stop is only available for running runs.
Actor shows "Unknown user"	The triggering user no longer exists in the system.	Normal display — no action needed.
"Deployment history" tab not visible	No Pipeline view permission.	Contact Admin to request access.
Screen shows "Nothing found"	The Pipeline has no deployments yet.	Perform at least one deployment first.
"View log" button is greyed out	The Deployment has no log yet.	No action needed.
"View run" button is greyed out	The Run ID no longer exists — the run has been deleted and can't be recovered.	No action needed.
"Cancel" option not shown or greyed out	The Deployment is not in a Processing state.	Cancel is only available for running deployments.
"Deployed by" shows "Unknown"	The triggering user no longer exists.	Normal display — no action needed.
"Deployed by" shows "System"	The deployment was triggered automatically.	Normal display for auto-deployment.
Deployment Detail panel shows a warning banner	Previous and Current belong to different Environments.	Expected — every field will differ between two different environments. Compare deployments within the same Environment instead.

See Pipeline history & logs.

Credentials, environments, scan jobs, and approval gates

Issue	Cause	Resolution
SonarQube connection fails to verify	Server URL or authentication token is incorrect.	Re-check the URL and generate a fresh token in SonarQube.
SonarQube scan job has no connections to select	No SonarQube connection has been created for the Project yet.	Create one under Credentials → SonarQube first.
Environment doesn't appear when configuring a Deploy Job	No Environment has been added under that cluster.	Add an Environment on the Environments tab first.
Trivy scan always fails the Security Gate	The selected severities match findings in the image.	Adjust the severity selection, or set "Continue with warning" instead of "Fail pipeline".
Approver can't approve their own run	Self-approval is blocked — the Actor and Approver are the same user.	Have a different user approve, or change the configured Approver.
Run auto-rejected at the Gate stage	No approval decision was made within the configured Timeout.	Re-run the Pipeline and approve within the timeout window.

See Manage credentials, Manage environments, Add a security scan job, Add an approval gate.