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

# Notification channel update errors

## Error Codes

These are the most common error cases and error codes returned by [Update Notification Channel](c_updateNotificationChannel) Process. Any of these error codes may be returned during the execution of this Process.

**Note:** See [Common Process Error Codes](c_commonProcessErrors).

| HTTP Status | Storefront Gateway Business Error Code | Field | Description |
| - | - | - | - |
| `412` | `no-available-authnId` | n/a | The Process was successfully invoked, but there are no other applicable authN IDs for the user to select. |
| `404` | `option-not-found` | n/a | The authN ID (i.e., email address or mobile number) specified by the client was not found or does not exist. |
| `400` | `NotEmpty` | `optionId` | In the [standard use case](c_useCaseUpdateChannel), the client invoked this Process, and then sent a Process Step request with an empty or null `optionId` parameter, where a number should have been specified. This field must not be null or empty. |
| `400` | `already-current-pnc` | `updatedContactChannel` | In the [single step use case](c_useCaseSingleStepNotification), the client specified an authN ID that is already the current user's primary notification channel. |
| `400` | `channel-not-activated` | `updatedContactChannel` | In the [single step use case](c_useCaseSingleStepNotification), the client specified an authN ID that exists, but does not yet have an `activated` status. The end user must first verify the channel before that channel would be a valid option. |
| `400` | `not-users-channel` | `updatedContactChannel` | In the [single step use case](c_useCaseSingleStepNotification), the client specified an The authN ID that is not registered to the current user. |
| `400` | `channel-type-not-supported` | `updatedContactChannel` | In the [single step use case](c_useCaseSingleStepNotification), the client specified an authN ID type that is not currently allowed to be the primary notification channel. Supported types are controlled by an internal **supportedNotificationChannelTypes** setting. By default, both email and mobile numbers are supported types that a user can set as their primary contact channel. Upon request, MarketONE can change this setting so that users can only select their email addresses or mobile numbers exclusively for notifications. |
| `400` | `ValidAuthnIdentifier` | `updatedContactChannel` | In the [single step use case](c_useCaseSingleStepNotification), the client invoked the Process without specifying an actual value for the `updatedContactChannel` parameter (either in the request URL or request body). This field must not be null or empty. |
| **Parent topic:**[Update Notification Channel Process](c_updateNotificationChannel) | | | |


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