I'm currently relying on pub/sub notifications for the activities collection to grab a variety of intraday activity data (include heartrate). All is going well on the normal activities endpoints, but when I pull the HR data it's usually not available for the most recent few minutes leading up to the notification. If I ask for data for the 15 minutes leading up to the notification's receipt, I'll have step/calorie/distance information for all 15 minutes, but I might only have heartrate data for the earliest 12 or 13 minutes of that window. If I "backfill" the heartrate data a few minutes later it's usually available. It doesn't look like there's currently an option to subscribe specifically to HR data, so I'm hoping to be able to use the activities collection as a notification for HR data as well.
Is this behavior expected? If so, is there an easy heuristic I can use to determine how long to delay fetching the heartrate data (and will a subscription for HR be coming in the future)? If not, any advice on how to troubleshoot the issue?
Thanks very much for any light you can shed on this.
EDIT: I should note that I'm using minute-level calls for the steps/calories/distance endpoints and second-level calls for the HR endpoint.
