Activity duration being greater than active duration

[msirbu]

Hello, we had a few instances recorded around March 8th 2021, where activity duration was initially greater that active duration and then getting corrected. 

I have couple questions on this:

1. Is duration, activeDuration or originalDuration expected to be change?

2. What's the explanation for duration getting changed in the example below?

3. Can activeDuration ever be greater than duration?

Here is our example:

activeDuration: 1222000 => 1222000
duration: 1226000 => 1226000
originalDuration: 1226000 => 1226000

Activity as first fetched from fitbit (some fields where deleted):

{
  "activeDuration": 1222000,
  "activityName": "Treadmill",
  "activityTypeId": 20049,
  "averageHeartRate": 133,
  "calories": 206,
  "distance": 1.823421,
  "distanceUnit": "Mile",
  "duration": 1226000,
  "elevationGain": 0,
  "hasActiveZoneMinutes": true,
  "lastModified": "2021-03-09T11:54:53.000Z",
  "logId": 38126004557,
  "logType": "tracker",
  "manualValuesSpecified": {
    "calories": false,
    "distance": false,
    "steps": false
  },
  "originalDuration": 1226000,
  "originalStartTime": "2021-03-09T05:34:03.000-06:00",
  "source": {
    "id": "124206406",
    "name": "Versa",
    "trackerFeatures": [
      "HEARTRATE",
      "STEPS",
      "CALORIES",
      "DISTANCE"
    ],
    "type": "tracker",
    "url": "https://www.fitbit.com/"
  },
  "speed": 5.371777414075287,
  "startTime": "2021-03-09T05:34:03.000-06:00",
  "steps": 2626,
}

  Activity after duration being corrected:

{
  "activeDuration": 1222000,
  "activityName": "Treadmill",
  "activityTypeId": 20049,
  "averageHeartRate": 133,
  "calories": 206,
  "distance": 1.823421,
  "distanceUnit": "Mile",
  "duration": 1350000,
  "elevationGain": 0,
  "hasActiveZoneMinutes": true,
  "lastModified": "2021-03-09T12:25:32.000Z",
  "logId": 38126004557,
  "logType": "tracker",
  "manualValuesSpecified": {
    "calories": false,
    "distance": false,
    "steps": false
  },
  "originalDuration": 1350000,
  "originalStartTime": "2021-03-09T05:34:03.000-06:00",
  "source": {
    "id": "124206406",
    "name": "Versa",
    "trackerFeatures": [
      "DISTANCE",
      "HEARTRATE",
      "STEPS",
      "CALORIES"
    ],
    "type": "tracker",
    "url": "https://www.fitbit.com/"
  },
  "speed": 5.371777414075287,
  "startTime": "2021-03-09T05:34:03.000-06:00",
  "steps": 2626,
}

[JohnFitbit · Accepted solution]

Hi @msirbu,

Welcome to the forums!

To answer your questions:

1. Is duration, activeDuration or originalDuration expected to be change?

• No, unless the Fitbit user decides to change the duration of the activity after they synced their data. For example, a user can go on a run but forget to end their activity. When they eventually complete the activity, they'll sync the data and you'll see the initial duration for that activity. The user can choose to update the activity and shorten the recorded activity to reflect the correct time, which then you'll see a new duration when the user applies the changes to the activity. 

2. What's the explanation for duration getting changed in the example below?

• See above. In the example you provided, it looks like the duration increased from one example to the next. The user could have updated the completed activity to make it longer. They could have ended the activity too early by mistake.

3. Can activeDuration ever be greater than duration?

• I don't believe activeDuration could be greater than duration since activeDuration is the time spent being above sedentary (light activity, moderate activity, intense activity) during an activity, while duration encompasses all activity levels including sedentary.

I hope this helps. Let me know if you need additional clarification.

[msirbu]

@JohnFitbitThanks for the quick reply and the explanation!

I just realized that I made a mistake and duration was never shorter than activeDuration in all of my examples. So this all makes sense now.