---
title: "Validate Project Key Check Failure when Integrating with a Third-Party Ticketing System"
slug: "validate-project-key-check-failure-when-integrating-with-a-third-party-ticketing-system"
updated: 2026-10-21T11:06:16Z
published: 2026-10-21T11:06:16Z
canonical: "resources.realtheory.io/validate-project-key-check-failure-when-integrating-with-a-third-party-ticketing-system"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://resources.realtheory.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Validate Project Key Check Failure when Integrating with a Third-Party Ticketing System

## Background

When running the configuration validation checks on a ticketing integration configuration in RealTheory, the **Validate Project Key** check fails with the following message:

`Check unsuccessful - Project does not exist`

This failure will prevent the integration from functioning correctly and usually signals an issue with the credentials, project permissions, or ticketing system environment rather than a formatting problem with the Project Key itself.

## Problem

While inline validation might appear successful, it does not verify whether the specified user has access to the project. The **Validate Project Key** check verifies that, and a check failure indicates that the named user cannot authenticate to the project or lacks the necessary permissions.

## Solution

Check for the following, and then retry the validation:

### Credential Issues

- An incorrect username or API token (secret).  

Confirm that the username/API token is correct and active.
- The user does not have permission to create issues in the specified project.  

Ensure the user has permissions to browse and create issues in the project.

### Ticketing System Project Issues

- Role-based access control (RBAC) or project-specific permissions prevent the user from accessing the project.  

Ensure the user has permissions to browse and create issues in the project.

### Ticketing System Environment or Connectivity Issues

- The ticketing system is temporarily unavailable or returning errors (maintenance, rate limiting, or misconfigured proxy).  

Verify that the ticketing system is accessible through other means.