Rejoignez l'AI + Data Tour pour bénéficier de formations pratiques, découvrir des témoignages clients concrets et échanger avec les experts produits Domo près de chez vous.
Dataset-level Caching Settings
Some datasets change every few minutes while others rarely change at all. Until now, caching was set at the Cloud Integration level; every dataset from that integration shared the same cache time-to-live (TTL). Tuning one meant creating and maintaining a separate integration. Otherwise, teams over-refreshed slow-changing data and paid for unnecessary queries, or under-refreshed fast-changing data and got stale results.
The new Data Caching tab in your Cloud Integration’s settings lets you set a TTL for each dataset individually, separate from the integration that sources it. This update lets you:
- Match caching to the data: Set different TTLs for different datasets without duplicating integrations
- Cut query costs: Stop refreshing slow-changing data that doesn’t need it.
- Keep fast-changing data fresher: Tune a dataset’s TTL independently of the rest of the integration
- Avoid wasted consumption: Domo checks freshness only when a dataset is queried and its TTL has expired, so idle data doesn’t trigger redundant checks
Learn more about configuring data freshness and caching in Cloud Integrations.
Domo transforms the way these companies manage business.








.png)
.png)