Product Updates
February 2026 product update: backfills now arrive newest first, and planned workouts reach Coros and Huawei
February 2026: backfills now deliver faster for improved onboarding experiences, planned workouts now reach Coros and Huawei, and Apple Health symptom tags are launched.
TL;DR: Your onboarding screen can now show a user their own real data within seconds of them connecting. Backfills deliver the last seven days first and then fill in the rest of the history working backwards, so the week the user actually remembers is the first thing to arrive. Planned workouts also reached Coros and Huawei this month, and Apple Health symptom tags began arriving in the daily payload.
Backfills now deliver faster for a better user experience
Here is the experience that changes: A user downloads your app, connects their health data, and lands on a screen that says their data is loading. In that moment the thing they care about is last night's sleep, and that is what Terra sends first.
From February, a historical pull starts with the most recent seven days and delivers them immediately, then continues backwards through the rest of the history in the background. The user's first screen can populate almost instantly with the week they actually remember, and the deeper history arrives while they are looking at it.
Nothing about the total amount of data changes, and nothing about how you receive it changes either. The payloads are the same payloads in the same shape; they simply arrive in a more useful order. If your onboarding currently blocks on a completion signal before showing anything, this is worth revisiting, because you can now show something good long before the pull finishes.
Planned workouts now reach Coros and Huawei
Two platforms were added as destinations for structured sessions in February. Coros was added to the supported set, and Huawei followed with a documented limitation worth knowing about: Huawei handles the date a workout is planned for differently from the others, so the support matrix records exactly what it accepts rather than leaving you to find out.
Alongside that, February brought an operations support matrix to the documentation: a plain table of which operations, such as creating, updating, reading, and deleting a planned workout, each platform actually supports. Some support all four, some support creation but not deletion because the workout lives on the device once it has synced. Knowing this up front changes how you design the feature. If a platform cannot delete, your product needs a story for what happens when a coach changes their mind, and it is much better to design that story deliberately than to discover the gap from a support ticket.
The matrix is in the provider compatibility page.
Apple Health lets people log symptoms directly on their phone or watch: headache, fatigue, nausea, shortness of breath, and a long list of others, including the cycle-related ones. These are self-reported rather than sensed, and for that reason they are some of the most valuable data in the whole payload, because they are the only place the person's own experience is recorded.
A recovery score that drops without explanation is a puzzle. A recovery score that drops on a day the person logged a headache and poor sleep is a story you can tell them. From February those tags come through in the daily payload for users connected through the iOS SDK.
Also in February
- Ultrahuman: the sleep score reported by the ring is now carried through in the sleep payload.
- Garmin: permission changes a user makes on Garmin's side are now recognised as they happen, so the connection state you hold always reflects what that user has actually agreed to share.
- Webhooks can be resent for users who have since disconnected, which is what you need when you are replaying a window after an outage at your end.
- Every destination type now carries its own icon in the dashboard, including Azure Blob Storage and Health Connect, which makes a screen holding a dozen connections far faster to read at a glance.
