---
title: "Troubleshooting"
section: "Deploys & Repos"
description: "Fixes for SmartestQA Deploys & Repos: repository form errors, Test connection failures, webhook errors from CI, and deploys that stay Not tested."
url: https://docs.smartestqa.ai/en/deployments-troubleshooting.html
audience: [customer, admin]
updated: 2026-11-08
keywords: "deploys repos error problem fix test connection token rejected 401 403 404 webhook invalid deploy token commitSha environment status not tested no pipeline environment commits missing service name"
---
# Deploys & Repos: Troubleshooting

Find the message or symptom you see. Each entry says why it happens, what to check and how to fix it. Messages from the Git connection and the webhook come from the server in Turkish; each entry gives the meaning.

## In short

**On this page you can**

- Fix repository form errors such as an invalid service name or a missing token.
- Read Test connection failures and what each one means.
- Fix webhook errors your CI log shows: 401, missing environment, bad SHA, unknown status.
- Find out why a deploy stays Not tested or has no commits.

**How to use it**

1. Copy the exact message from the screen or the CI log.
2. Find it below (use the browser’s search for a word of the message).
3. Check the listed points in order.
4. Apply the fix, then deploy again or click Refresh .

## Repository form

### Problem: “Repository URL is required.” _(Repository)_

- **Fix:** Paste the address of the repository in [**Repository URL**](https://docs.smartestqa.ai/en/deployments-repos.html#fields). See [URL formats](https://docs.smartestqa.ai/en/deployments-repos.html#url-formats).

### Problem: “Service name: lowercase letters, digits, - or _ (e.g. web, api).” _(Repository)_

- **Why:** The [service name](https://docs.smartestqa.ai/en/deployments-repos.html#fields) is empty, longer than 40 characters, starts with `-` or `_`, or contains spaces or other characters.
- **Fix:** Use a short key such as `web`, `api` or `auth-service`. Upper case is turned to lower case for you.

### Problem: “Bu projede 'web' servis adiyla baska bir repo var.” (another repository in this project uses this service name) _(Repository)_

- **Why:** Service names are unique in a project, so deploys of two repositories never mix in one row.
- **Check:** The [**Code repositories**](https://docs.smartestqa.ai/en/deployments-repos.html#add-repo) list: the chip `Service: web` shows which repository already uses it.
- **Fix:** Pick another name, or edit the existing repository with [Settings](https://docs.smartestqa.ai/en/deployments-repos.html#change-repo) instead of adding a second one.

### Problem: “Enter an access token or choose "Deploy notification only".” _(Repository)_

- **Why:** A new repository with [**Connect with token**](https://docs.smartestqa.ai/en/deployments-repos.html#connection-modes) needs a token.
- **Fix:** Paste a read-only token ([which one](https://docs.smartestqa.ai/en/deployments-repos.html#token-types)), or switch to [**Deploy notification only**](https://docs.smartestqa.ai/en/deployments-repos.html#connection-modes). You can add a token later.

### Problem: “Repo adresi {sahip}/{repo} icermeli.”, “Azure DevOps adresi .../{proje}/_git/{repo} bicminde olmali.” or “Repo adresi http(s) olmali.” _(Repository)_

- **Why:** The address must contain owner and repository; Azure DevOps addresses must contain `/{project}/_git/{repo}`; only `http`, `https` and `git@host:owner/repo` are accepted. Related: “Repo adresinde sunucu adi yok.” (no host name) and “Repo adresi gecersiz.” (the address cannot be read).
- **Fix:** Copy the address from the repository’s page in your browser, as in [URL formats](https://docs.smartestqa.ai/en/deployments-repos.html#url-formats). If the server is not one of the listed providers, choose **Other**.

### Problem: **Add environment** does nothing _(Repository)_

- **Why:** The name is already in the list, or it has characters other than letters, digits, `-` and `_`, or it is longer than 32 characters. Invalid names are ignored without a message.
- **Fix:** Type a name such as `STAGING` or `UAT-2`. A repository can map 12 environments; more gives “En fazla 12 ortam eslenebilir.” (at most 12 environments).

### Problem: “Could not load.” or “Could not save.” _(Page)_

- **Why:** The request failed without a more specific reason, usually because the session expired or the connection dropped.
- **Fix:** Click **Refresh**. If it repeats, log in again. If you are a User without access to this project, ask an admin for [project access](https://docs.smartestqa.ai/en/company-settings-roles.html).

### Problem: “Select a project from the header to manage its agents.” _(Page)_

- **Fix:** No project is selected. Pick one in the header; repositories belong to a project.

## Test connection and commits

These messages appear under **Test connection**, or in an amber box in the [deploy detail](https://docs.smartestqa.ai/en/deployments-overview.html#deploy-detail) when commits could not be read.

### Problem: **Test connection** is greyed out _(Connection)_

- **Fix:** Fill [**Repository URL**](https://docs.smartestqa.ai/en/deployments-repos.html#fields) and type a token. When you edit a repository with a saved token, the button works with the saved one.

### Problem: “Token reddedildi (HTTP 401). Yetkiyi ve suresini kontrol edin.” (token rejected; check its rights and expiry) _(Connection)_

- **Why:** The provider refused the token (HTTP 401 or 403): it expired, was revoked, lacks read rights, or belongs to another provider.
- **Check:** 1. The token type matches the [provider table](https://docs.smartestqa.ai/en/deployments-repos.html#token-types).
  2. A GitHub fine-grained token includes this repository.
  3. Bitbucket app passwords are written as `username:app-password`.
- **Fix:** Create a new read-only token, paste it in [Settings](https://docs.smartestqa.ai/en/deployments-repos.html#change-repo) and click **Test connection**.

### Problem: “Repo ya da commit bulunamadi (HTTP 404)…” (repository or commit not found) _(Connection)_

- **Why:** The URL is wrong, the token cannot see the repository (providers answer 404 instead of 403), or a commit CI reported was never pushed to the provider.
- **Fix:** Check the URL and the token’s scope. In the deploy detail, check that CI sends the SHA of a pushed commit, then use [**Read commits again**](https://docs.smartestqa.ai/en/deployments-overview.html#deploy-detail).

### Problem: “Git sunucusuna ulasilamadi…”, “Git sunucusu zamaninda yanit vermedi.” or “Sunucu adi cozumlenemedi: …” (cannot reach, no answer in time, host name unknown) _(Connection)_

- **Why:** The SmartestQA server cannot reach your Git server: it is inside your network, a firewall blocks it, or the name only resolves internally.
- **Fix:** Allow SmartestQA to reach the Git server’s API, or use [**Deploy notification only**](https://docs.smartestqa.ai/en/deployments-repos.html#connection-modes): deploys are still recorded, only commits are missing.

### Problem: “Bu adrese istek atilamaz: …” (requests to this address are not allowed) _(Connection)_

- **Why:** The address points to the server itself (loopback such as `localhost`) or to a link-local address. These are blocked for security.
- **Fix:** Use the Git server’s real host name or private network address in the URL or the [API base URL](https://docs.smartestqa.ai/en/deployments-repos.html#self-hosted).

### Problem: “Git sunucusu yonlendirme dondu (HTTP 3xx). API adresini kontrol edin.” or “Git sunucusunun yaniti JSON degil. API adresini kontrol edin.” (redirect, or not a JSON answer; check the API address) _(Connection)_

- **Why:** The address answers with a login page or a redirect instead of the API. SmartestQA does not follow redirects.
- **Fix:** Set [**API base URL (self-hosted)**](https://docs.smartestqa.ai/en/deployments-repos.html#self-hosted) to the API root, for example `https://git.acme.local/api/v4` for GitLab. Use `https://` if the server redirects from `http://`.

### Problem: “Git sunucusu hata dondu (HTTP 500).” (the Git server returned an error) or “Connection test failed.” _(Connection)_

- **Fix:** The provider had an error, or the request failed. Try again in a few minutes; check the provider’s status page.

### Problem: “Commit list is shown when the repository is connected with a token.” _(Commits)_

- **Why:** The repository uses [**Deploy notification only**](https://docs.smartestqa.ai/en/deployments-repos.html#connection-modes) or the provider is Other.
- **Fix:** Open the repository’s [Settings](https://docs.smartestqa.ai/en/deployments-repos.html#change-repo), choose [**Connect with token**](https://docs.smartestqa.ai/en/deployments-repos.html#connection-modes), paste a token and save. Open the deploy again; older deploys get their commits when you open them. Provider Other never reads commits.

### Problem: “Commit listesi okunamadi.” or “Kayitli commit listesi okunamadi.” (the commit list could not be read) _(Commits)_

- **Fix:** Click [**Read commits again**](https://docs.smartestqa.ai/en/deployments-overview.html#deploy-detail) in the [deploy detail](https://docs.smartestqa.ai/en/deployments-overview.html#deploy-detail). If it repeats, run **Test connection** in the [repository’s Settings](https://docs.smartestqa.ai/en/deployments-repos.html#change-repo).

## Webhook errors from CI

These appear in your CI log, in the `message` of the response. The ready-made steps end with `|| true`, so the deploy itself still succeeds; only the record is missing.

### Problem: HTTP 401 “Gecersiz deploy token'i.” (invalid deploy token) _(Webhook)_

- **Why:** The token is missing, mistyped, was replaced with [**Generate new token**](https://docs.smartestqa.ai/en/deployments-ci.html#regenerate), or its repository was deleted.
- **Check:** 1. The header is `X-Deploy-Token` (or `Authorization: Bearer sdt_…`).
  2. The CI secret starts with `sdt_` and has no space or line break.
  3. The last four characters match “Token ending in …” in [**CI code & deploy token**](https://docs.smartestqa.ai/en/deployments-ci.html#add-ci-step).
- **Fix:** [Generate a new token](https://docs.smartestqa.ai/en/deployments-ci.html#regenerate) and update the CI secret.

### Problem: HTTP 400 “environment gerekli (DEV, TEST, PRP ...).” (environment required) _(Webhook)_

- **Why:** `environment` is empty or has characters other than letters, digits, `-` and `_`.
- **Fix:** Send `"environment":"TEST"` (or DEV, PRP, or your own name). See [the fields](https://docs.smartestqa.ai/en/deployments-ci.html#webhook).

### Problem: HTTP 400 “commitSha 7-64 karakterlik hex olmali.” (commitSha must be 7–64 hex characters) _(Webhook)_

- **Why:** The SHA is empty (the CI variable was not set), shorter than 7 characters, or is a branch or tag name.
- **Fix:** Use the commit variable of your CI: `${{ github.sha }}`, `$CI_COMMIT_SHA`, `${env.GIT_COMMIT}`.

### Problem: HTTP 400 “Bilinmeyen status: … (success | failure | cancelled | started)” (unknown status) _(Webhook)_

- **Fix:** Send one of the [accepted values](https://docs.smartestqa.ai/en/deployments-ci.html#statuses), or leave `status` empty for success. Jenkins’ `SUCCESS`/`FAILURE` work; `UNSTABLE` does not, so map it first as the ready-made Jenkins step does.

### Problem: HTTP 400 “deployedAt ISO-8601 olmali (ornek 2026-10-06T21:59:00Z).” (deployedAt must be ISO-8601) _(Webhook)_

- **Fix:** Send `2026-11-06T18:59:00Z`, a time with offset (`+03:00`), Unix seconds or milliseconds, or leave it out to use the arrival time.

### Problem: HTTP 400 “Govde bos.” (empty body) _(Webhook)_

- **Fix:** Send the JSON body with `Content-Type: application/json`. In shells, check that quotes around the `-d` value survived.

### Problem: CI ran but nothing appears; the chip still says **No deploy received yet** _(Webhook)_

- **Check:** 1. The CI log of the notify step: an error message above means one of the entries on this page.
  2. The step ran at all: it must be after the deploy and run always (`if: always()`, `when: always`, `post { always }`).
  3. The URL is the **Webhook URL** of this SmartestQA server, with `POST`.
  4. You clicked **Refresh**: the page does not update by itself.
- **Fix:** Run the **curl** tab’s command from the CI machine to see the answer directly.

## Test state

### Problem: A deploy stays **Not tested** although a pipeline ran _(Overview)_

- **Why:** The run is outside the deploy’s [window](https://docs.smartestqa.ai/en/deployments-numbers.html#tested-window) or in another environment.
- **Check:** 1. The [pipeline](https://docs.smartestqa.ai/en/schedule-create.html)’s environment is the deploy’s environment (TEST is not PRP).
  2. The run started after the deploy time. If CI sends `deployedAt`, check its time zone.
  3. No newer successful deploy of the same repository arrived before the run.
  4. It was a pipeline run, not a [dry run](https://docs.smartestqa.ai/en/automate-dry-run.html) in Automate.
  5. You clicked **Refresh**.
- **Fix:** Run the pipeline in the right environment after the deploy. To make this automatic, start a pipeline from CI after the notify step, or let an [Autonomous Agent](https://docs.smartestqa.ai/en/ai-agents.html) react to deploys.

### Problem: **No pipeline environment** _(Overview)_

- **Why:** The deploy went to an environment of your own, such as STAGING. [Pipelines](https://docs.smartestqa.ai/en/schedule-create.html) run only in DEV, TEST or PRP, so nothing can be matched.
- **Fix:** If STAGING is where your TEST pipelines run, send `"environment":"TEST"` from CI. Otherwise the cell shows the version only; that is expected. See the [effect on the KPI cards](https://docs.smartestqa.ai/en/deployments-numbers.html#kpi-cards).

### Problem: “Last deploy failed” under a green chip _(Overview)_

- **Why:** The newest deploy failed or was cancelled, so the previous successful version still runs. The chip describes that version. See [Cell states](https://docs.smartestqa.ai/en/deployments-numbers.html#cell-states).
- **Fix:** Open [**Deploy history**](https://docs.smartestqa.ai/en/deployments-overview.html#history) and the failed row, then [**Open CI run**](https://docs.smartestqa.ai/en/deployments-overview.html#deploy-detail) to see why it failed.

### Problem: A repository has no row in the grid, or deploys are missing from it _(Overview)_

- **Why:** The repository was deleted (its records stay in the history only), or CI uses the token of another repository, so the deploys land in that repository’s row.
- **Fix:** Add the repository again and put its new token in CI. Check that each CI job uses the token of its own repository.

### Problem: The deploy token is not shown any more _(Token)_

- **Why:** SmartestQA shows a token only once. It keeps a fingerprint, not the token.
- **Fix:** If CI still works, nothing to do. If you need the value, [generate a new token](https://docs.smartestqa.ai/en/deployments-ci.html#regenerate) and update CI.
