> For the complete documentation index, see [llms.txt](https://docs.tryterra.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryterra.co/faq/help-topics/data-api-sdk/extra-features-scores-graphs-teams-nutrition-cgm/garmin-planned-workout-lifecycle.md).

# How do Garmin planned workouts handle completion and updates?

Terra's Garmin planned-workout adapter uses Garmin's **Workout Schedule endpoint**.

Garmin's public Training API has **no completion endpoint**, so a pushed workout stays on the calendar until you **DELETE it**.

* **Delete key:** the composite `scheduleID`/`workoutID`. A peeled `workoutID` returns **424 Failed Dependency** because the schedule entry still references the template.
* **Updates:** re-posting with an existing `provider_workout_id` and a new `planned_date` reschedules. Changing workout content requires **delete-then-recreate**.

See the [Planned Workouts API core concepts](https://docs.tryterra.co/planned-workouts-api/core-concepts).