# February Update 2026

Check out what we've been doing at Terra over the month of February 2026!

### Backend 💾 <a href="#backend" id="backend"></a>

#### Features <a href="#features" id="features"></a>

* ​Added elevation summary and heart rate data for Huawei integration
* Improve initial data backfill system
  * Most recent 7 days are requested first
  * The rest are then filled in month by month in reverse chronological order

#### Bugs <a href="#bugs" id="bugs"></a>

* Fixed a bug where activity duration for peloton may be 0. Added a fallback to compute this from length of video watched.
* Fixed an issue where units for speed in laps for were incorrectly set as km/h
* Fixed a bug where blood pressure samples had incorrect timestamps for Apple Health
* Updated request to Decathlon API (missing header)
* Fixed a bug where TCX files were requested eventhough permission was not granted by user

***

### SDKs <a href="#sdks" id="sdks"></a>

#### iOS <a href="#android" id="android"></a>

* Added symptom tracking as tags data in daily payloads

***

### Dashboard <a href="#dashboard" id="dashboard"></a>

* A brand new UI update on our [dashboard](https://dashboard.tryterra.co) is live!&#x20;
  * Much more intuitive and sleek design

***

### Landing Page <a href="#landing-page" id="landing-page"></a>

* Added AI Page discussing AI in healthtech!
  * <https://tryterra.co/ai>
* New research on marathon running.&#x20;
  * <https://tryterra.co/research/predicting-marathon-race-pace>


---

# 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/2026/february-update-2026.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.