Changelog

4 min read Updated Aug 2026 14 languages

22 August 2026 #

Organization managers can now create and manage daily-step, points/sports, and combined challenges in the mobile app, including cover images, schedules, visibility, sharing, participant lists, results, and ending an event.
Hosts can buy challenge capacity through the App Store or Google Play. New events select a total tier and paid events can add 10, 25, 50, 100, or 250 places; interrupted activation can be retried without another charge. See Upgrading participant limits.
The app is now available in 16 languages, and Profile → Your events reflects actual registrations even before a result exists.
Android Health Connect background access can periodically send missing daily steps while the app is not open. Foreground sync remains available if the optional permission is declined; workout import remains foreground-only.

In-person race organizers can now move a race to another date or cancel it, publish a notice, shift selected deadlines, notify by email/SMS, offer mapped transfers, and review secure refund requests and batches.
Team challenges can enable member-shared invite links and QR codes. A valid invite preselects the member's team and can bypass private/join codes, so the organizer controls whether the feature is enabled.
Participant-created public teams can be created inside mobile challenge registration. Duplicate enrollments in the same challenge distance are now blocked while distinct multi-distance entries remain supported.
Challenge dates now consistently use the hosting organization's timezone. After a challenge starts, its start is locked and the original end can be extended by at most three days.
The anonymous homepage event-creation form was removed. Creating an event now requires a signed-in organization manager; simple challenges can also be created in the app.
The challenge results API now includes per-sport breakdowns for participant, team, and team-member results, with sport-aware team column descriptors.

Participants affected by an in-person race change can use a secure response link to keep their entry, request a mapped transfer, or request a refund, depending on the organizer's policy and entry eligibility.
Mobile challenge results now include participant and team tabs, team member drill-down, credited activities, per-sport totals, and a result-sharing action.
Team members can share their own invite link/QR, and joined participants can leave a challenge directly in the mobile app.
Virtual route results now mark finishers with a checkered flag and can filter people or teams by Warming Up, On track, and At the Finish.
Daily step emails no longer describe a missing step record as zero or a 100% shortfall; they say that steps have not been received and prompt the participant to open the app.
Checkout keeps the buyer-entered email when a reused participant profile has no email. Email matching is case-insensitive, and sign-in credentials are not copied into participant names.

Google Health (Beta) is available as a separate, read-only connection for daily activity and exercise sessions, with optional GPS access and an explicit in-product data-use disclosure. It is separate from Google sign-in.
Provider synchronization, standings recalculation, result delivery, workout-upload deduplication, bib assignment, push delivery, QR scanning, clipboard handling, and social sign-in recovery received reliability improvements.

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.

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.

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.

Was this page helpful?

Thanks — your feedback helps us improve these docs.