---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/30113#article
headline: "30113: Specified date is too old"
url: https://www.twilio.com/docs/api/errors/30113
inLanguage: en
dateModified: 2026-04-20T06:23:21.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 30113: Specified date is too old

Log Type: APPLICATION

Log Level: ERROR

## Description

Twilio returns this error when you request a Deactivations report for a date earlier than `2020-08-27`. Deactivations data is only available from August 27, 2020 onward for the Deactivations resource.

### Possible causes

* The `Date` parameter is earlier than `2020-08-27`.
* Your application is backfilling deactivation data beyond the earliest date Twilio stores.
* A default value, timezone conversion, or date calculation in your application produced an older date than intended.

### Possible solutions

* Update the `Date` parameter to `2020-08-27` or later.
* Validate request dates in your application before calling the Deactivations resource.
* If you are running a historical import, limit requests to the available reporting window and skip dates before `2020-08-27`.
* Verify that your application sends the expected calendar date in `YYYY-MM-DD` format.

#### Additional resources

* [Deactivations resource](/docs/messaging/api/deactivations-resource)
* [Handling Deactivated Phone Numbers](https://help.twilio.com/hc/en-us/articles/360042744973-Handling-Deactivated-Phone-Numbers)
* [Programmable Messaging API overview](/docs/messaging/api)