Cache Timespan is tied to step completion because the flow data you are caching gets stored on the outcome of the step itself. Therefore, this timespan just designates how long the outcome of the data remains within the cache of this step at completion. To answer your question, if this step completed at 5:00 AM, the cache would be cleared at 10:00 PM.
See our documentation here: https://documentation.decisions.com/docs/outcome-caching
Cache Timespan
How does the cache timespan feature work on a step? For instance, is this static so the cache will clear at 5:00 PM every day, or is this cache scheduled to clear every 17 hours even if not used?
Comments
-
Cache Timespan is tied to step completion because the flow data you are caching gets stored on the outcome of the step itself. Therefore, this timespan just designates how long the outcome of the data remains within the cache of this step at completion. To answer your question, if this step completed at 5:00 AM, the cache would be cleared at 10:00 PM.
See our documentation here: https://documentation.decisions.com/docs/outcome-caching
-
@cookie clicker 2 Thank you for your answer.
Howdy, Stranger!
Categories
- 4.3K All Categories
- 74 General
- 13 Training
- 206 Installation / Setup
- 1.1K Flows
- 110 Rules
- 268 Administration
- 212 Portal
- 496 General Q & A
- 709 Forms
- 344 Reports
- 3 Designer Extensions
- 48 Example Flows
- 57 CSS Examples
- 1 Diagram Tile
- 7 Javascript Controls
- 184 Pages
- 5 Process Mining
- New Features
- 186 Datastructures
- 70 Repository
- 229 Integrations
- 28 Multi-Tenant
- 27 SDK
- 81 Modules
- 58 Settings
- 25 Active Directory
- 12 Version 7
- 35 Version 8
- 143 Lunch And Learn Questions