> 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/changelog/2025/readme-2.md).

# May Update 2025

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

## Backend 💾

### Features

* Added laps for Wahoo data
* Added "isWebUpload" as manual activity workout for Garmin Workouts
* Added checks for Third Party upload workouts to Withings

### Bug fixes

* Fix an issue with authentication for EatThisMuch Users
* Fixed an issue where webhook retries weren't retried correctly
* Fixed a bug where deauth events weren't sent for Health Connect users

## Blood Biomarkers

* Added \~150 standardized enums for units for biomarkers
* Increase processing speed for blood lab reports by \~ 200% (reports take half the time to be processed)
* Add classification for reference ranges (i.e. option for having "borderline" reference ranges along with "normal" and "abnormal")
* Standardize dates + times of sample collection in reports
* Improve parsing of a wider range of blood reports

## Health Scores

* Fixed an issue where Apple Health HRV data were not taken into consideration correctly due to SDNN/RMSSD differentiation

***

## SDK 📱

### [TerraiOS](ref:reference-ios-sdk)

* Specify workout predicates for activities retrieved. This ensures all samples in the activity payload is linked to that specific workout only
* Updated background delivery system to fetch further back if data is synced late into Apple Health

### TerraAndroid

* Requests to Health Connect are now made more efficient (less likely to hit rate limits)
* Fixed an issue where sometimes TerraAndroid causes a crash due to rate limits from Health Connect

***

## Frontend📺

### Dashboard

* Access Blood Biomarkers Product directly from our dashboard!


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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/readme-2.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.