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

# 54100: Document not found

Log Level: ERROR

## Description

Twilio returns this error when your request targets a Sync Document that does not exist in the specified Sync Service. You can address a Document by its `sid` or `unique_name`, and a Document can stop being available after you delete it or after its `ttl` expires.

### Possible causes

* The request uses an incorrect Document `sid` or `unique_name`.
* The request may be using the wrong `ServiceSid` for the Document you are trying to access.
* The Document was deleted and is no longer available through the REST API.
* The Document expired after a `ttl` value was set.

### Possible solutions

* Verify that the request includes the correct `ServiceSid` and the correct Document identifier for that service. A fetch request must target the Sync Service that owns the Document and use either the Document `sid` or its exact `unique_name`.
* If you use a Document SID, confirm that you are passing a valid Sync Document SID that begins with `ET`.
* If you use `unique_name`, confirm that the value matches the Document name exactly.
* If the Document was deleted or expired, create the Document again before retrying the request.
* If you need the Document to remain available, do not set `ttl`, or send a new `ttl` value when you update the Document. By default, Sync data is permanent unless you delete it or configure expiration.

#### Additional resources

* [Document Resource](/docs/sync/api/document-resource)
* [Sync Objects Time-To-Live (TTL)](/docs/sync/objects-ttl)
* [State Synchronization with Sync Objects](/docs/sync/objects-overview)