How duplicate detection works and solutions for common import errors.
Duplicate detection
A file is treated as a duplicate when an existing session matches on:
- Track name
- Car name
- Session type
- Session date
- Finish position
Duplicates are skipped during import — they are not re-added. This prevents the same session from appearing twice in your history.
Re-importing a session
To import again:
- Delete the session from your history
- Upload the XML file again
Common issues
| Issue | Solution |
|---|---|
| No matching driver | Match Settings → Driver name to <Name> inside <Driver> in the XML — see Driver matching (special characters, contact support if it persists) |
| Already imported | Session exists — delete first to re-import |
| Invalid file name | Rename to standard LMU format — see File locations |
| File too large | Max 10 MB per file |
| No new sessions added | All files were duplicates or had no matching driver |
| Too many files | Max 500 per manual upload — use Sync Agent |
| Invalid XML | File must be a valid LMU session result with rFactorXML and RaceResults elements |
| Empty file | Re-export or re-run the session in LMU |
Error details
After an import job completes, expand Error Details in the upload panel to see per-file failure reasons.
Preflight checks
Before upload, MyLMU may preflight files and report:
- Files already imported
- Files with unexpected names
- Files that will be skipped
Get more help
- FAQs — import section with detailed answers
- Contact support — if driver matching still fails after checking Settings and the XML
<Name>tag (include your driver name and any special characters)