---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/80602#article
headline: "80602: Non Unique Service Name"
url: https://www.twilio.com/docs/api/errors/80602
inLanguage: en
dateModified: 2026-06-08T12:04:59.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 80602: Non Unique Service Name

Log Level: WARNING

## Description

This warning appears when you try to create a Proxy Service with a `uniqueName` that is already assigned to another Service. In Proxy, `uniqueName` is an application-defined identifier for the Service. It must be unique and 191 characters or fewer.

### Possible causes

* The create request used a `uniqueName` that already belongs to another Proxy Service in your account.
* Your application tried to create a new Service for an environment or workflow that already has an existing Service with that name.
* You intended to reuse or update an existing Service, but sent a create request instead.

### Possible solutions

* Create the Service with a different `uniqueName`.
* List your existing Services before creating a new one so you can confirm the name is available.
* If the Service already exists, reuse that Service instead of creating another one with the same `uniqueName`.
* If you need to change an existing Service, update the Service by SID instead of creating a second Service with the same `uniqueName`.
* Use a naming convention that keeps Service names distinct across environments such as dev, stage, and prod.

#### Additional resources

* [Proxy API overview](/docs/proxy/api)
* [Service resource](/docs/proxy/api/service)
* [Proxy overview](/docs/proxy)