# Can we specify a TTL for validations?

**URL:** <https://discourse.greatexpectations.io/t/can-we-specify-a-ttl-for-validations/496>\
**Category:** Archive\
**Created:** [November 13, 2020, 10:45pm UTC](https://discourse.greatexpectations.io/t/can-we-specify-a-ttl-for-validations/496 "2020-11-13T22:45:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bhcastleton](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.greatexpectations.io/bhcastleton/32/73_2.png) [@bhcastleton](https://discourse.greatexpectations.io/u/bhcastleton)\
**Post date:** [November 13, 2020, 10:45pm UTC](https://discourse.greatexpectations.io/t/can-we-specify-a-ttl-for-validations/496/1 "2020-11-13T22:45:24Z")

</div>

Is there a way to specify some sort of TTL for validations, to automatically remove validations that ran say over a month ago when building data docs?

---

<div class="post-metadata">

**Author:** ![bhcastleton](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.greatexpectations.io/bhcastleton/32/73_2.png) [@bhcastleton](https://discourse.greatexpectations.io/u/bhcastleton)\
**Post date:** [November 13, 2020, 10:48pm UTC](https://discourse.greatexpectations.io/t/can-we-specify-a-ttl-for-validations/496/2 "2020-11-13T22:48:45Z")

</div>

Great Expectations doesn’t currently have this feature in the open source project.  
Check out the post on the validation\_results\_limit data docs config option in case that can help for your workflow.

> [@What does the validation\_results\_limit option in Data Docs limit?](https://discourse.greatexpectations.io/t/what-does-the-validation-results-limit-option-in-data-docs-limit/310):
>
> Does the validation\_results\_limit data docs config option limit the number of HTML files in the validations backend store or does it just limit the number that get included in the index? For example, if I had over 1000 validations in my validations store, would validation\_results\_limit: 1000 keep the number of files in data\_docs/validations under 1000? and if not, is there a workaround to make sure that the website backend store doesn’t grow too large?