Custom activity fields not populating for most recent activity [Confirmed bug]

Bug Reports
1

I use a number of custom activity fields for my runs, things like xEff, run/walk percentage, VO2 max est, etc.

However, for my most recent run none of these fields have populated (they all have ?). For every previous run all of these fields are populated.

I have tried re-analyze and I also tried deleting and reload from Strava, but all the fields are still ?

Everything else in the activity like heart rate and pace and elevation etc all look totally normal.

Does anyone have any ideas what might be happening here?

2

Fixed. I introduced a bug yesterday that stopped custom activity fields from being computed for people with no custom interval fields. Sorry about that and thanks for the report.

Anyone else with this issue: Just re-analyse existing activities missing custom activity field values to fix. This should only happen to stuff downloaded on the 2 or 3rd of July 2025.

2 Likes
3

Thank you for the quick fix!

1 Like
4

Hi, any chance that this got reintroduced somehow? Having the same issue now with only yesterday’s activity, everything before that working normally

5

Hmm… Checked for my custom activity fields and they are copied over for the Ride and Gravel Ride (I have a separate Gravel cat) category, but they’re not for the Run category.
I’m talking about the same fields for all categories, HRrest and BRmin, coming from morning wellness measurement.

6

It’s a Run for me as well. Interval fields are working normally. But not activity fields. If I go to the Javascript of the custom activity field and click the little play button, it calculates it exactly as it should, but in the activity view it just shows ‘?’ even after re-processing the file

7

@david @eva
Was this picked up?

8

If any of the fields fail by exceeding memory or CPU limits, then field processing stops at that field. That is probably what happened. We need to add an error field to the activity to report this in the UI.

1 Like
9

Actually it isn’t as bad as that. If a field goes over the limits and then fails to stop, then processing stops.

2 Likes