Data Freshness

Patchly syncs data from your Microsoft environment on a regular schedule. This page explains how often data is updated and what “freshness” means for your findings.

Sync Schedule

Data Type	Frequency	Typical Delay
Vulnerabilities	Nightly (02:00 UTC)	< 24 hours
Device inventory	Nightly (02:00 UTC)	< 24 hours
User directory	Nightly (02:00 UTC)	< 24 hours
Software inventory	Nightly (02:00 UTC)	< 24 hours
Security alerts	Nightly (02:00 UTC)	< 24 hours

After each sync, Patchly automatically runs enrichment and scoring. Your dashboard typically reflects the previous day’s state.

What “Fresh” Means

Status	Meaning
Fresh (< 24 hours)	Data was synced within the last day. This is the normal state.
Aging (24-48 hours)	Data is slightly behind. Usually resolves with the next nightly sync.
Stale (> 48 hours)	Something may have interrupted the sync. Contact Patchly support.

The dashboard header shows a freshness indicator so you always know how current your data is.

Why Nightly?

Nightly syncs provide a good balance between data currency and API usage:

Vulnerability data changes relatively slowly — most CVEs don’t change day-to-day
Device inventory is stable enough that daily snapshots capture meaningful changes
Nightly processing allows enrichment, scoring, and curation to complete before your workday

If you need more frequent updates for your use case, contact your Patchly representative.

What Happens During a Sync

Pull: Patchly fetches the latest data from your Microsoft Defender and Graph APIs
Store: Raw data is written to secure, versioned storage
Enrich: Vulnerability findings are matched against NVD, EPSS, and KEV databases
Score: Devices and users receive updated criticality scores
Curate: All data is combined into the enriched findings view shown in your dashboard

This entire process typically completes within 15-30 minutes.

Freshness in the Dashboard

The dashboard displays data age in the header:


Last updated: 6 hours ago

If you see data older than 48 hours, contact support@patchly.ai.