Skip to main content
Junction sends historical.data.{RESOURCE}.in_progress after a historical chunk finishes ingestion for a resource. For example, historical.data.sleep.in_progress reports a completed sleep chunk. Use this notification to fetch the completed dates through the Data Access API while older history is still loading. The event contains dates and identifiers, not the resource’s data records.

When events are sent

  • A successfully processed non-final chunk can emit a progress event, including when the provider returns no data for those dates.
  • The final chunk uses the existing historical.data.{RESOURCE}.created completion event instead. A backfill consisting of one chunk has no progress event.
  • A failed chunk does not emit a progress event.
Progress events apply to supported backend historical pulls. Garmin, Apple HealthKit and Health Connect SDK syncs, and workout streams fetched through follow-up jobs do not report chunk progress through this event. The device resource does not emit historical progress or completion events. Device notifications use provider.device.created and provider.device.updated.

Payload

The event uses the standard webhook envelope. The following fields are inside data: Dates use YYYY-MM-DD. The completed chunk dates describe one chunk, not all history completed so far. Completion means the chunk was processed; it does not mean the provider had records for every date in that chunk.
Oura sleep progress
For this event, query the Sleep API for the user and oura provider, using October 15 through November 13 as the date range. You do not need to wait for the older history to finish. Subscribe to the relevant historical.data.{RESOURCE}.in_progress event types in your webhook endpoint configuration. Keep your existing historical.data.{RESOURCE}.created subscriptions to receive the final notification. The existing completion event and its start_date / end_date fields are unchanged.

Progress in the tracker

The Historical Pulls API and the Dashboard’s Range Completed column aggregate completed chunk dates. They show the earliest start and latest end reported so far, rather than a list of individual chunks. Permanently failed chunks may leave gaps within these bounds.