# 30130: Messaging Service SID already belongs in another domain configuration.

Log Type: APPLICATION

Log Level: ERROR

## Description

This error occurs when you try to associate a `MessagingServiceSid` with a Link Shortening domain configuration, but that Messaging Service is already associated with another domain configuration in your account. Link Shortening works with Messaging Services, and the `MessagingServiceSid` you use must be associated with the correct Link Shortening domain.

### Possible causes

* The `MessagingServiceSid` in your request is already associated with a different Link Shortening domain configuration.
* You selected a Messaging Service in Console that is already configured for Link Shortening under another domain.
* Your API request used the wrong `MessagingServiceSid` when you sent a `POST` request to the Link Shortening domain's Messaging Services subresource.

### Possible solutions

* Open Console, go to Messaging > Messaging Services, select the Messaging Service, and review the Link Shortening domain assigned to it. If the Messaging Service is already attached to another domain, keep that association or choose a different Messaging Service.
* If you want to use this Messaging Service with a different Link Shortening domain, remove the existing domain association first, then associate the Messaging Service with the correct domain.
* If you use the API, verify the `MessagingServiceSid` before sending the request. If needed, retrieve the current domain configuration for that Messaging Service so you can confirm which domain already owns the association.
* If you need multiple domains for different use cases, create separate Messaging Services and associate each one with the appropriate Link Shortening domain.

#### Additional resources

* [Link Shortening Onboarding Guide](/docs/messaging/features/link-shortening/onboarding-guide)
* [Link Shortening](/docs/messaging/features/link-shortening)
* [Messaging Services](/docs/messaging/services)