> ## Documentation Index
> Fetch the complete documentation index at: https://www.seam.co/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Unmanaged Errors and Warnings

> Unmanaged errors and warnings in the Seam API, with code meanings and example objects for diagnosing integration issues.

## Errors

Each error is an object with the following shape:

```json Example error theme={"dark"}
{
  "error_code": "failed_to_issue",
  "message": "Indicates that Seam was unable to issue this access method before its access grant started, so the recipient may be unable to access the space. This usually points to a problem that needs attention, such as an offline or disconnected device. Seam keeps retrying, and this error clears automatically if the access method is eventually issued.",
  "created_at": "2025-01-01T00:00:00.000Z"
}
```

> [accordion] Error object properties
>
> **error\_code** `Enum (String)`
>
> Unique identifier of the type of error. Enables quick recognition and categorization of the issue.
>
> One of the error codes listed below.
>
> **message** `String`
>
> Detailed description of the error. Provides insights into the issue and potentially how to rectify it.
>
> **created\_at** `String (ISO 8601)`
>
> Date and time at which Seam created the error.

### `access_not_provisioned`

Indicates that the access system rejected the access that Seam tried to set up for this access method, so its credential cannot open the affected entrances, even after it is issued. For example, a hotel room may already be reserved or checked in for another guest. The message contains the reason that the access system gave. Seam keeps retrying, and this error clears automatically once the access system accepts the access.

***

### `failed_to_issue`

Indicates that Seam was unable to issue this [access method](https://www.seam.co/docs/use-cases/granting-access/creating-an-access-grant.md) before its access grant started, so the recipient may be unable to access the space. This usually points to a problem that needs attention, such as an offline or disconnected device. Seam keeps retrying, and this error clears automatically if the access method is eventually issued.

***

## Warnings

Each warning is an object with the following shape:

```json Example warning theme={"dark"}
{
  "warning_code": "being_deleted",
  "message": "Indicates that the access method is being deleted.",
  "created_at": "2025-01-01T00:00:00.000Z"
}
```

> [accordion] Warning object properties
>
> **warning\_code** `Enum (String)`
>
> Unique identifier of the type of warning. Enables quick recognition and categorization of the issue.
>
> One of the warning codes listed below.
>
> **message** `String`
>
> Detailed description of the warning. Provides insights into the issue and potentially how to rectify it.
>
> **created\_at** `String (ISO 8601)`
>
> Date and time at which Seam created the warning.
>
> **new\_code** `String`
>
> The PIN code that was assigned instead.
>
> **original\_access\_method\_id** `String (UUID)`
>
> ID of the original access method from which this backup access method was split, if applicable.
>
> **original\_code** `String`
>
> The originally requested PIN code that could not be used.

### `being_deleted`

Indicates that the [access method](https://www.seam.co/docs/use-cases/granting-access/creating-an-access-grant.md) is being deleted.

***

### `delay_in_issuing`

Indicates that Seam has not yet issued this [access method](https://www.seam.co/docs/use-cases/granting-access/creating-an-access-grant.md), even though its access grant is about to begin, so access may not be ready when the recipient arrives. Seam is still attempting to issue it, and this warning clears automatically once issuance succeeds.

***

### `pulled_backup_access_code`

Indicates that all attempts to create an access code on this device before the start time failed and a backup access code was used to ensure access was provided in time.

***

### `requested_code_unavailable`

Indicates that the access system could not use the PIN code requested for this [access method](https://www.seam.co/docs/use-cases/granting-access/creating-an-access-grant.md), for example because it did not meet the access system's PIN rules, so the access system assigned a different code. Give the recipient the assigned code.

***

### `schedule_rounded_up`

Indicates that the access system can only end card access on fixed time marks, so access was extended past `ends_at` to the next mark. The message states when access actually ends.

***

### `updating_access_times`

Indicates that the access times for this [access method](https://www.seam.co/docs/use-cases/granting-access/creating-an-access-grant.md) are being updated.

***

### `user_identity_missing_email_address`

Indicates that the access system delivers this mobile key through an app invitation sent to the recipient's email address, but the [user identity](https://www.seam.co/docs/capability-guides/mobile-access/managing-mobile-app-user-accounts-with-user-identities.md) for this [access grant](https://www.seam.co/docs/use-cases/granting-access/creating-an-access-grant.md) has no email address, so the mobile key cannot be delivered. Set an email address on the user identity when you create the access grant.

***

### `user_identity_missing_phone_number`

Indicates that the access system delivers this mobile key to the recipient's phone number, but the [user identity](https://www.seam.co/docs/capability-guides/mobile-access/managing-mobile-app-user-accounts-with-user-identities.md) for this [access grant](https://www.seam.co/docs/use-cases/granting-access/creating-an-access-grant.md) has no phone number, so the mobile key cannot be delivered. Set a phone number on the user identity when you create the access grant.

***


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.