Skip to content

Markdown

Sync and delivery

A workout change can be saved on your iPhone while still waiting for Apple Watch. Local save, companion delivery, account cloud sync, and Workout Sync (WorkoutKit) confirm different outcomes. Success in one does not mean the others have finished.

Four different outcomes

Local save means Momentum saved the workout change on this device. It does not confirm delivery to another device or an account upload.

Companion delivery moves supported workout changes and plan information between iPhone and Apple Watch. It requires Momentum on the paired devices, not a Momentum account.

Account uploads concern account-backed copies in Momentum Cloud. They require a signed-in Momentum account and account cloud sync enabled on the device. An account upload is separate from Apple Watch delivery.

Workout Sync (WorkoutKit) sends eligible upcoming workouts to Apple's Workout app. It requires Apple's authorization and a compatible workout. Sending a planned workout is not recording a completed workout.

Read the state that answers your question

During a strength workout on iPhone, these status details describe different stages:

  • Saved on This iPhone confirms the local save.
  • Waiting to Send means the change has not reached Apple Watch.
  • Waiting for Confirmation means the change left iPhone but Apple Watch has not confirmed it yet.
  • Available on Apple Watch means Apple Watch confirmed the saved changes.

The Live Connection state describes current reachability, not whether a change saved locally. Losing that connection does not invalidate a local save.

Sync Center reports account upload status. Signing in does not itself confirm an upload, and a pending change is not an uploaded change.

What a confirmation does not prove

Apple Watch delivery is not a complete account backup. Neither a local save nor a companion confirmation establishes a copy in Momentum Cloud.

Workout Sync does not send Momentum strength sets, reps, load, or rest because Apple's Workout app cannot represent them. Authorization alone also does not prove that Apple accepted every eligible workout.

These distinctions explain confirmed states, not a guarantee of delivery time or identical support across devices. Check the affected state before recreating a workout; do not delete local history to resolve a delivery delay.

Follow the workout, not just the transfer

Momentum public documentation