with one click
omnistudio-cache-strategies
// Configure caching on DataRaptors and Integration Procedures to cut response times, with cache-bust and freshness guarantees. NOT for platform-level org cache.
// Configure caching on DataRaptors and Integration Procedures to cut response times, with cache-bust and freshness guarantees. NOT for platform-level org cache.
[HINT] Download the complete skill directory including SKILL.md and all related files
| name | omnistudio-cache-strategies |
| description | Configure caching on DataRaptors and Integration Procedures to cut response times, with cache-bust and freshness guarantees. NOT for platform-level org cache. |
| category | omnistudio |
| salesforce-version | Spring '25+ |
| well-architected-pillars | ["Performance","Reliability"] |
| triggers | ["dataraptor cache","integration procedure cache","omnistudio cache ttl","cache bust omniscript"] |
| tags | ["omnistudio","cache","performance"] |
| inputs | ["current response times per IP/DR","data freshness requirements"] |
| outputs | ["cache config + bust strategy + monitoring"] |
| dependencies | [] |
| runtime_orphan | true |
| version | 1.0.0 |
| author | Pranav Nagrecha |
| updated | "2026-04-28T00:00:00.000Z" |
OmniStudio supports caching per-record on DataRaptors (cache duration in minutes) and Integration Procedures (cache-enabled flag with TTL). Used correctly, cache cuts 50–90% of repeated calls; used wrong it serves stale data. This skill walks through identifying read-heavy paths, choosing a TTL aligned to business freshness tolerance, implementing a deterministic cache-bust on mutation, and monitoring hit ratio so the cache's contribution is observable.
Read-heavy IPs/DRs where source data changes infrequently (product catalog, reference data).
CacheMgmt.references/examples.md)references/gotchas.md)references/llm-anti-patterns.md)