${maxPace} for indoor activities about core HOT 7 CLOSED

@zecanard nothing has changed recently. Just to make sure: the correct tag is ${paceMax} and not ${maxPace}. Same for ${paceAvg}, ${speedAvg} and ${speedMax}. Can you please confirm that you're using the right tags? If so, I'll investigate it further.

from core.

Yes, sorry, I typed that from memory, but I am using the correct tags in my rule. I also use the same rule for all my runs, so that part shouldn’t be an issue.

from core.

Can you please go to https://strautomator.com/activities/debug and try it with an older activity (that had the paceMax) and a newer one which is missing? I'll do some tests later tonight to see if Strava is messing up with their API data. It happened a few times before.

from core.

The debug page shows a value for ${paceMax} in both cases. After further investigation, it’s my blank weather tags that interfere with ${paceMax}.

If I put ${paceMax} by itself, or with tags that have an actual value (eg. ${speedMax}), everything’s good. If I add ${weather.start.summary}, then ${paceMax} is blank.

I recently consolidated my rules to add the weather tags on all my activities, then have them removed by another service when missing (I have my reasons for this). That is when ${paceMax} started getting blanked-out.

I can easily split my rules back up, so it’s not a big deal. But it’s still possible that this issue interferes with other tags, as well.

from core.

I split my rule into indoor/outdoor and got the correct value for today’s indoor run. However, with a weightlifting workout, ${paceMax} got printed out as ${paceMax} instead of getting blanked out.

This is also no big deal, and I can easily work around it. But there definitely seems to be something going on with that specific statistic.

from core.

Issue flagged as stale for being inactive for 28 days, please report status if this is still relevant.

from core.

Issue closed due to inactivity, feel free to update and re-open it if necessary.

from core.