Per-user events cron persist
Last updated 2026-06-14
Definition
Per-user events cron persist is the scheduled job that saves each person’s events into the Atlas journey store on a regular cadence. Rather than rebuilding everything live each time you open a profile, Quri keeps per-user history written down and current, so timelines and funnels load from stored data instead of a slow fetch.
How to do this in Quri
- Connect your sources so Quri has per-user events to persist.
- Let the scheduled job run on its cadence to write each person’s events to the store.
- Open /app/atlas/users — profiles load from the persisted store, not a live re-fetch.
- Check timestamps on a profile to confirm the latest run has landed.
Frequently asked
- Why persist per-user events on a schedule instead of fetching live?
- Live fetching across every source for every profile is slow and repetitive. The scheduled job writes events down once, so timelines and funnels open fast from stored data.
- How fresh is the data on a profile?
- As fresh as the last scheduled run. Between runs you see the stored snapshot. If a tenant has no graph yet, Quri can build one on demand instead of waiting for the next run.