You can see this error in many different scenarios. The error occurs when the API name of the custom element you create has the same API name as another custom element.
Here’s an example scenario.
You create a custom setting with a Label of App Config and an Object Name of AppConfig.
You try to create a custom metadata type with a label of App Config and an Object Name of AppConfig.
On the custom metadata type page, you see this error: "That object name is already in use"
This error occurs because the custom setting and the custom metadata type both have the same API name.
API names must be unique across these custom elements within a single org:
Big objects
Custom events
Custom metadata types
Custom objects
External objects
Custom settings
Knowledge article types
002330968

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.