# November Update 2025

Check out what we've been doing at Terra over the month of November 2025!

## Backend 💾

### Temporarily Disabled:

* Freestylelibre
  * We have had to disable Freestyle Libre integration due to ongoing issues at the moment with Abbott.

### Features

* OMRON now provides information about the devices used during measurements
* Updated MapMyFitness API to use its mapmyfitness.com domain instead of the ua.com domain (deprecated by MapMyFitness)
* Ride ID is appended to summary ID of workouts now for Peloton

### Bugs

* Fixed an issue where if no samples are available in Hammerhead workouts, the workout is skipped in sending
* Fixed an issue with planned workouts for TrainingPeaks where if the workout has no "Steps" or "Structure" it is skipped.
* Fixed a bug where Sleep payloads for Suunto may contain duplicated payloads
* Fixed a bug where "older" Peloton workouts weren't fetched correctly

***

## SDKs

### Apple

* Added retries for workout fetching to account for:
  * Cases when Fitness App syncs samples late to Health App
  * Cases where fetching workouts were not successful then skipped
* Ensure 12 AM to 12AM requests for days affected by Daylight saving

### Android

* Fixed an issue where Samsung Health may write 0 steps into Health Connect, causing an `IllegalArgumentException` to be thrown when we try to read steps data.&#x20;

***

## Dashboard

* Fixed a bug where `Usage` page does not reflect custom contract credits correctly
* Updated Terms of Services on our site. On visiting, you will be prompted about this!

***

## Landing Page

* Updated Terms of Services on our site. On visiting, you will be prompted about this!


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tryterra.co/changelog/2025/november-update-2025.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
