# In Discovery: Time Based Refresh

**URL:** <https://developer.sailpoint.com/discuss/t/in-discovery-time-based-refresh/78906>\
**Category:** In Discovery\
**Tags:** identity-security-cloud, in-discovery-closed, new-enhancement\
**Created:** [August 30, 2024, 6:52pm UTC](https://developer.sailpoint.com/discuss/t/in-discovery-time-based-refresh/78906 "2024-08-30T18:52:47Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![KJR1](https://avatars.discourse-cdn.com/v4/letter/k/9de0a6/32.png) [@KJR1](https://developer.sailpoint.com/discuss/u/KJR1)\
**Post date:** [August 30, 2024, 6:52pm UTC](https://developer.sailpoint.com/discuss/t/in-discovery-time-based-refresh/78906/1 "2024-08-30T18:52:47Z")

</div>

**Business Problem**  
Previously, Identity Security Cloud would leverage a pre-defined time for refreshing target identities. For global organizations supporting multiple time zones, this pre-determined timing was not flexible enough to effectively support their need to perform joiner-mover-leaver events on a specific local time that was applicable for that identity.  
With the introduction of Time-Based Refresh, administrators can now control the desired local time of refresh for targeted identities based on a given time attribute (Next Processing Date), which means less identifies must be refreshed at one time. ISC can now support identity state changes in different local times.

**How You Can Help**  
We are continuing to validate our understanding of the problem space and our solution. Our Product Management team is opening a closed preview for customers throughout the month of September to exercise the feature and give us direct feedback on improvements. If you are interested in joining the preview, please complete our closed preview form by _September 6th_, [Time Based Refresh Closed Preview Form](https://app.smartsheet.com/b/form/8adc2ec1a5fb4c30b8019b35ea3b766f).

---

<div class="post-metadata">

**Author:** ![Mccarney](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/mccarney/32/14953_2.png) [@Mccarney](https://developer.sailpoint.com/discuss/u/Mccarney)\
**Post date:** [September 3, 2024, 9:50am UTC](https://developer.sailpoint.com/discuss/t/in-discovery-time-based-refresh/78906/2 "2024-09-03T09:50:01Z")

</div>

Hi Kristen,

With the proposed changes, will it still be possible to trigger refreshes based on account aggregation or will this scheduling functionality replace it?

Best Wishes

Ryan

---

<div class="post-metadata">

**Author:** ![yael\_kadoshi](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/yael_kadoshi/32/1399_2.png) [@yael\_kadoshi](https://developer.sailpoint.com/discuss/u/yael_kadoshi)\
**Post date:** [September 5, 2024, 5:30pm UTC](https://developer.sailpoint.com/discuss/t/in-discovery-time-based-refresh/78906/3 "2024-09-05T17:30:02Z")

</div>

there is no change for manual refresh or refresh that runs from aggregation. This use case is specifically to enhance JML which runs as part of batch refresh (8am / 8pm)

---

<div class="post-metadata">

**Author:** ![KJR1](https://avatars.discourse-cdn.com/v4/letter/k/9de0a6/32.png) [@KJR1](https://developer.sailpoint.com/discuss/u/KJR1)\
**Post date:** [September 6, 2024, 3:33pm UTC](https://developer.sailpoint.com/discuss/t/in-discovery-time-based-refresh/78906/4 "2024-09-06T15:33:42Z")

</div>

Hello everyone! Thank you to all of the people that signed up to join our closed preview! We look forward to your feedback. At this time, closed preview registration is now closed.