Clarity session data freshness: missing processing status for newly recorded sessions

Microsoft Clarity records sessions client-side and uploads them asynchronously. The project dashboard and Export API both reflect sessions only after server-side processing completes. On the free tier as of 2024, this delay is commonly reported to range from 30 minutes to 2 hours, and may extend to 24 hours under high load. No public SLA or configuration knob is documented to reduce this latency.

The tracking script's own browser cache (max-age=300) does not affect session visibility; stale dashboard results stem from the server-side aggregation pipeline. Filtering by date range queries a pre-aggregated column store, so newly processed sessions appear only after the next aggregation cycle. This creates uncertainty for consumers who need to know when a specific session ID becomes queryable.

An unresolved product decision is whether Clarity should expose a processing status indicator or webhook. Because this behavior is not covered by a public SLA, the following questions require current verification:

• Does the Clarity Export API expose a per-session processing timestamp or status field?
• Is there any documented configuration or project setting that affects the aggregation cycle or processing latency?
• What mechanism, if any, allows a consumer to determine when a recorded session has become queryable without polling the dashboard?