> For the complete documentation index, see [llms.txt](https://developer.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.collibra.com/api/graphql/data-access/object-types/issue.md).

# Issue

Represents an issue in Collibra Data Access. An issue can be created by the system when a potential problem is detected.

```graphql
type Issue {
  createdAt: Time!
  entity: IssueEntity!
  entityId: ID!
  entityType: EntityType!
  issueLevel: IssueLevel!
  issueType: IssueType!
  message: String!
  otherEntities: [IssueOtherEntity!]!
  otherEntityId: String @deprecated
  otherEntityType: EntityType @deprecated
  structuredError: StructuredError
}
```

### Fields

#### createdAt ● [`Time!`](/api/graphql/data-access/scalars/time.md) non-null scalar <a href="#created-at" id="created-at"></a>

The time at which the issue was initially raised.

#### entity ● [`IssueEntity!`](/api/graphql/data-access/unions/issue-entity.md) non-null union <a href="#entity" id="entity"></a>

The entity object on which the issue occurs.

#### entityId ● [`ID!`](/api/graphql/data-access/scalars/id.md) non-null scalar <a href="#entity-id" id="entity-id"></a>

The ID of the entity on which the issue occurs.

#### entityType ● [`EntityType!`](/api/graphql/data-access/enumerations/entity-type.md) non-null enum <a href="#entity-type" id="entity-type"></a>

The type of the entity on which the issue occurs.

#### issueLevel ● [`IssueLevel!`](/api/graphql/data-access/enumerations/issue-level.md) non-null enum <a href="#issue-level" id="issue-level"></a>

The severity level of the issue.

#### issueType ● [`IssueType!`](/api/graphql/data-access/enumerations/issue-type.md) non-null enum <a href="#issue-type" id="issue-type"></a>

The type of issue.

#### message ● [`String!`](/api/graphql/data-access/scalars/string.md) non-null scalar <a href="#message" id="message"></a>

The message describing the issue.

#### otherEntities ● [`[IssueOtherEntity!]!`](/api/graphql/data-access/object-types/issue-other-entity.md) non-null object <a href="#other-entities" id="other-entities"></a>

The list of additional entities the issue may be linked to.

#### otherEntityId ● [`String`](/api/graphql/data-access/scalars/string.md) deprecated scalar <a href="#other-entity-id" id="other-entity-id"></a>

> **WARNING - DEPRECATED**

Use otherEntities instead. Resolved from the first element of otherEntities.

The ID of an optional additional entity the issue may be linked to.

#### otherEntityType ● [`EntityType`](/api/graphql/data-access/enumerations/entity-type.md) deprecated enum <a href="#other-entity-type" id="other-entity-type"></a>

> **WARNING - DEPRECATED**

Use otherEntities instead. Resolved from the first element of otherEntities.

The type of an optional additional entity the issue may be linked to.

#### structuredError ● `StructuredError` object <a href="#structured-error" id="structured-error"></a>

The categorised error behind this issue, when the agent provided one. Prefer this over message when present; it carries the category, hint, affected resource and missing permissions.

### Member Of

[`IssueEdge`](/api/graphql/data-access/object-types/issue-edge.md) object


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.collibra.com/api/graphql/data-access/object-types/issue.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.