# 80603: Non Unique Session Name

Log Type: APPLICATION

Log Level: ERROR

## Description

You receive this error when you create a Proxy Session with a `uniqueName` that is already used by another Session in the same Service. A Session `uniqueName` is an application-defined identifier and must be unique.

### Possible causes

* Another Session in the same Service already has the `uniqueName` you sent in the create request.
* Your application retried Session creation with the same `uniqueName`.
* Your application generated the same identifier for more than one Session.

### Possible solutions

* Generate a new `uniqueName` before you create the Session.
* Use a value that is unique for each Session in the Service, such as a distinct order ID or job ID from your application.
* Verify whether a Session with that `uniqueName` already exists in the Service before you create a new one.
* If you intended to continue an existing conversation, reuse the existing Session instead of creating another Session with the same `uniqueName`.

#### Additional resources

* [Proxy Session resource](/docs/proxy/api/session)
* [Proxy quickstart](/docs/proxy/quickstart)
* [The Proxy API overview](/docs/proxy/api)