Skip to contentSkip to navigationSkip to topbar
Page toolsOn this page
Looking for more inspiration?Visit the

80603: Non Unique Session Name


ERROR: 80603

error-80603 page anchor
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.

Possible causes

possible-causes page anchor
  • 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.
  • 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

additional-resources page anchor