How are cached results of Explores affected when a datagroup transitions to a triggered state?

When a datagroup transitions to a triggered state, any cached results of Explores associated with that datagroup are invalidated. This is because the triggered state indicates that there has been a change in the underlying data, and the system needs to ensure that users are seeing the most current and accurate information. By invalidating the cached results, Looker forces a refresh, ensuring that the next query run against the Explore will retrieve up-to-date data.

Maintaining or reversing the cached results would not serve the purpose of ensuring data accuracy during crucial updates. Leaving them unchanged could lead to users querying stale data, which can significantly impact decision-making processes based on outdated information. Thus, invalidation is a necessary step to preserve data integrity and ensure that users have access to the most relevant insights.