Cache

herbe.calendar maintains a local cache of ERP data and calendar sync state to reduce load on external systems and keep the calendar responsive. Most of the time the cache manages itself. Occasionally you need to invalidate it manually.

What is cached

• ERP data — activity groups, pipeline structures, person codes, and related reference data fetched from the ERP. Refreshed on every scheduled cron sync.
• Calendar sync state — incremental sync tokens from Outlook and Google, used to fetch only changes since the last sync rather than re-fetching everything.

When to invalidate manually

The most common reason: ERP data changed but the change didn't trigger a webhook and the next scheduled sync hasn't run yet.

Invalidate the cache if:

• An ERP change (new activity group, renamed stage, updated person code) isn't reflected in the calendar after 15+ minutes.
• You've added a new ERP connection and want to populate data immediately.
• You're troubleshooting a sync issue and want to rule out stale cache.

How to invalidate

Go to Admin → Cache.

• Invalidate ERP cache — clears all cached ERP reference data. The next request triggers a fresh fetch from ERP. There may be a brief delay on the next calendar load while the cache rebuilds.
• Invalidate sync state — clears incremental sync tokens for Outlook or Google. The next sync for that connection runs a full re-fetch rather than a delta. Use this only if you suspect the sync token is corrupted; full re-fetches are slower and put more load on the external API.

Both options take effect immediately.