> 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/help-center/help-topics/data-api-sdk/extra-features-scores-graphs-teams-nutrition-cgm/planned-workout-424-and-retries.md).

# Why does scheduling a planned workout return 424, and is it retried?

A 424 when scheduling a planned workout means Terra couldn't confirm the push and saved nothing. Terra does not retry it.

**A `424` from `POST /workouts/{workout_id}/plan` means Terra couldn't confirm the push and saved nothing. Terra does not queue or retry it.**

The error message tells you which case you hit:

* **The provider rejected the workout**, for example a message containing `garmin rejected workout` followed by the provider's reason. The provider refused the workout as sent, so change the workout. Reconnecting the user won't help.
* **`workout with this name already exists on the user's Garmin account`**. Garmin needs a unique workout name per user.
* **`failed to push workout to provider device`** or **`something went wrong while writing planned workout`**. A general failure writing to the provider for that user. The workout may still have reached the device, so check the user's device before sending it again.

Other responses from the same call:

* **`404`** **`this connection does not support planned workouts`**: the user's provider doesn't accept planned workouts.
* **`400`** when `planned_date` is missing or isn't `YYYY-MM-DD` or an ISO 8601 timestamp.

Adjustments Terra makes to fit a provider, such as a target the provider can't use, don't cause a `424`. The call succeeds and lists them in `warnings`. See [coercion warnings](https://docs.tryterra.co/planned-workouts-api/coercion-warnings) and [provider compatibility](https://docs.tryterra.co/planned-workouts-api/provider-compatibility).