Changelog

29 July 2026 #

Organizers and whitelabels #

• Challenge organizers can now create, rename, and delete teams directly from the Teams tab. Deleting a team removes its assignments but keeps participants and their results.
• Discount codes can require a minimum number of participants in the cart. Participant tickets count toward the threshold; merchandise does not.
• Challenge participant exports now include each participant's join code on the Total and stage sheets.
• Whitelabel portals can use the expanded challenge results API for leaderboards, heatmaps, detailed results, route shapes, statistics, head-to-head comparisons, activity splits, and analytics, subject to the challenge's privacy settings.

Participants and scoring #

• Combined challenge scoring now uses the club timezone for workout days and avoids counting the same walking or running distance twice: for each day, it uses the larger of workout distance and step-derived distance.
• Step game daily tasks now consistently evaluate daily-step records rather than workout result rows.
• Activity processing now corrects implausible GPS jumps caused by recording gaps, excluding both unverifiable distance and the corresponding time. This can make the accepted DistantRace total lower than the source app's total.
• Challenge message-board photo uploads now support HEIC and HEIF images from iPhones.
• During checkout, DistantRace now reuses a matching saved participant profile connected to the signed-in buyer instead of creating a duplicate.
• Workouts recorded in the mobile app now preserve average heart-rate data when available; see Recording workouts.

Accounts, integrations, and payments #

• Organizer access now enforces SMS two-factor authentication when it is the configured second factor. One-time-code autofill and sign-in emails were also improved.
• Sports-provider synchronization and disconnection are more reliable, including retries and cleanup when a provider connection is removed. See Sync troubleshooting.
• Malformed or unknown payment-return data now shows the normal payment-error message and redirects participants back to checkout instead of producing a server error. See Online payment transactions.