---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/54200#article
headline: "54200: Map not found"
url: https://www.twilio.com/docs/api/errors/54200
inLanguage: en
dateModified: 2026-06-08T11:29:20.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 54200: Map not found

Log Level: ERROR

## Description

Twilio returns this error when your request targets a Sync Map that does not exist in the specified Sync Service. You can address a Sync Map by its `sid` or its `unique_name`, and the lookup happens within the Service in the request path.

### Possible causes

* The `sid` or `unique_name` in your request does not match an existing Sync Map.
* The request uses the wrong `ServiceSid`, so Twilio looks for the map in a different Sync Service.
* The Sync Map was deleted manually.
* The Sync Map expired and was deleted after its `ttl` or `collection_ttl` elapsed.

### Possible solutions

* Verify that you are sending the correct `ServiceSid` for the Sync Service that contains the map.
* Confirm that the map identifier is correct. Use the exact Sync Map `sid` or `unique_name` that was assigned to the resource.
* List the Maps in the target Service to confirm that the resource exists before you fetch, update, or delete it.
* If the map expired or was deleted, create a new Sync Map and update your application to use the current identifier. If you need the map to remain available, review your `ttl` or `collection_ttl` settings.

#### Additional resources

* [Map Resource](/docs/sync/api/map-resource)
* [Service Resource](/docs/sync/api/service)
* [The Sync REST API](/docs/sync/api)