Stale Cache Data Returned by IFTTT Google Calendar Trigger

When an IFTTT applet that uses the Google Calendar trigger fires, the event data sometimes reflects an older calendar state rather than the most recent change made in the calendar.

The goal is to determine whether the observed delay is caused by IFTTT’s internal caching of trigger evaluations and, if so, to understand the cache’s behavior and any available ways to force a fresh evaluation without recreating the applet.

Constraints include the lack of direct access to IFTTT’s cache‑management interface, unknown time‑to‑live values for the Google Calendar trigger, and the inability to modify the underlying service’s polling frequency from the applet configuration.

What is the typical cache lifetime or refresh interval for the Google Calendar trigger in IFTTT?

Can manually triggering a test event or re‑saving the applet bypass the cached result and obtain current data?

Are there documented limits or recommendations for avoiding stale cache outcomes when relying on near‑real‑time calendar changes?