Skip to main content

​
Overview

Fasten Connect automatically caches the records it retrieves on your behalf. During the cache lifetime the platform serves subsequent requests for the same connection_id directly from the cache, preventing redundant network calls to the source system and improving response times for you and your users.

​
Cache lifetime

  • The default cache duration is 24 hours from the moment the record is first retrieved.
  • While the cache entry is active, repeat requests for that record are fulfilled from the cached payload.
  • Once the 24 hour window elapses, the system deletes the cached copy automatically. A follow-up request after that point triggers a fresh retrieval and repopulates the cache for another 24 hour cycle.

​
Operational notes

  • You do not need to manage cache eviction; the platform handles expiration and cleanup.
  • If you need to guarantee the most current data, wait for the existing cache to expire or request support for a manual refresh.
  • Monitor your integration for stale data if you are surfacing rapidly changing records to end users, and adjust user-facing messaging accordingly.