Skip to content
Customer portal
Contact
  • There are no suggestions because the search field is empty.

Timing Service matching but not populating

Issue

The timing service fails to populate timing information to an event because an existing session has already been matched in the stream.

Error Message

You may see this errorin the timing service:

 {session_str} matched to {best.display_string} but already populated and not a linked session

Cause

This error occurs when a new session matches to a session that has already been populated in the stream. This rare issue typically happens when the timing provider declares the same session twice but with different names.

Solution

There are two approaches to resolve this issue:

Option 1: If the first matched session was a mistake

  1. Stop the laptime service configuration (or local deployment)
  2. Flush the relay
  3. Delete any existing laps/runsheets if necessary
  4. Restart the configuration/local deployment

Option 2: If you need to merge the sessions

  1. Stop the configuration/local deployment
  2. Find the desired session in the configuration
  3. Enable the "Merge Timing Sessions" option for that session
  4. Save the configuration
  5. Restart the configuration/local deployment