80603: Non Unique Session Name
ERROR
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.
- Another Session in the same Service already has the
uniqueNameyou 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.
- Generate a new
uniqueNamebefore 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
uniqueNamealready 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.