# Nexus cache policies **URL:** \ **Category:** Sonatype Nexus Repository\ **Tags:** cache\ **Created:** [July 17, 2019, 9:30am UTC](https://community.sonatype.com/t/nexus-cache-policies/2182 "2019-07-17T09:30:03Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![ado](https://yyz1.discourse-cdn.com/flex047/user_avatar/community.sonatype.com/ado/32/769_2.png) [@ado](https://community.sonatype.com/u/ado)\ **Post date:** [July 17, 2019, 9:30am UTC](https://community.sonatype.com/t/nexus-cache-policies/2182/1 "2019-07-17T09:30:03Z")
Hello good people! I want to ask a question. As far as we using Nexus it’s very great to have proxy repositories and cache packages inside of the Nexus for quick access them later. Great feature, thank Sonatype for that! Question is: Can we configure somehow this cache policies? I mean, for example: PyPi proxy repository Some package, let’s say `awesomePyPi1.0.0.tar.gz` We use this package for our build and it was downloaded and cached inside Nexus. A few days later new version of package was introduced and uploaded to a proxy repo with `awesomePyPi1.1.1.tar.gz` And we still using this package in our build. What will happen when the code triggered to build? Will the cached version be in use or 1.1.1 will be downloaded and cached instead? Second question: can we configure somehow time that cached packages are stored in global?(for example 1 week) and per repository?(for example: 1 week for PyPi and 1 month for NuGet?) Can’t find this in documentation so if someone will provide me a link for that - that will be cool. --- _[View the full topic](https://community.sonatype.com/t/nexus-cache-policies/2182)._