Clarify caching behavior based on support ticket patterns

[torimwhaley]

Summary

• Adds a note that results caching is not enabled by default, even on paid plans, with guidance on how to check
• Clarifies that caching applies instance-wide (not per-project or per-dashboard)
• Adds that Google Sheets syncs also use cached results (missing from the original list)
• Explains that cache expiry is rolling, not scheduled — based on age since last refresh, not a fixed daily time
• Adds a tip for teams reporting on "yesterday's data" to use shorter cache durations
• Fixes a typo ("whebnever" → "whenever")

Context

These clarifications are based on recurring patterns in closed support tickets over the past 4 months (Oct 2025 – Feb 2026), where customers repeatedly asked questions that could have been answered by clearer docs:

• Customers asking "is caching enabled for us?" with no way to self-check
• A customer whose Google Sheets syncs started delivering stale data after caching was enabled
• A customer confused about why their "yesterday's data" dashboards showed old numbers until mid-afternoon

Test plan

• Verify the page renders correctly in Mintlify preview
• Confirm the Note, Tip, and formatting display properly

[github-actions]

🤖 Documentation Bot

✅ All checks passed! No issues found.

[github-actions]

🤖 Documentation Bot

✅ All checks passed! No issues found.