Troubleshoot Common Issues
Quick solutions to the most common issues users encounter in Adrenaline. From registration problems to timing quirks, this guide helps you diagnose and fix issues fast. If you don't find your issue here, contact support.
Registration & Check-In Issues
Rider Can't Register Online
Symptoms: "Registration unavailable" or error when submitting
Common Causes:
- Registration deadline passed
- Classes full (capacity limits met)
- Event set to "Officiate Registration Only"
- Missing required fields (machine info, emergency contact)
Solutions:
- Check event settings → "Online Registration" is enabled and deadline hasn't passed
- Review class capacity limits—increase if needed
- Ensure all required fields are present in registration form
- Clear browser cache and try again
- Try different browser (Chrome/Edge recommended)
Rider Not Showing in Check-In List
Symptoms: Rider says they registered but aren't in check-in
Common Causes:
- Registration incomplete (didn't submit, payment failed)
- Registered for wrong event
- Using wrong search term (name vs. number)
Solutions:
- Search by number plate, first name, and last name separately
- Check "All Registrations" view (not just "Checked In")
- Ask rider to show confirmation email with registration ID
- Manually add rider via "Officiate Registration" if needed
Number Plate Already Taken
Symptoms: "Number plate already in use" error
Solutions:
- Check if another rider registered with that number
- If duplicate is incorrect, edit that registration to change number
- Rider must choose different number or contact other rider to resolve
Race Control & Timing Issues
Automated Timing Not Working (No Crossings)
Symptoms: Riders running but no crossings detected
Common Causes:
- Riders' phones location services not enabled or accuracy too low
- Track not properly configured (no timing zones)
- Riders not running the race with Adrenaline app
Solutions:
- Verify track has finish line configured (TrackLang or manual setup)
- Ask riders to check: Location services enabled, location permission granted to app, high accuracy mode on
- Ensure riders opened app and "joined" the race (not just spectating)
- Check cellular/internet connection—timing data needs to upload
- Run ad-hoc test race to verify track timing zones work
AI Vision Not Detecting Riders
Symptoms: Camera feed visible but no detections
Common Causes:
- Camera angle too extreme or obscured view
- Poor lighting (too dark, backlit, glare)
- Camera not defined in TrackLang
- Low resolution or frame rate
Solutions:
- Check camera angle: should be perpendicular, not more than 60° tilt
- Improve lighting: avoid shooting into sun, add artificial lighting if needed
- Verify camera defined in TrackLang with correct position, heading, tilt, FOV
- Use minimum 1080p @ 30fps (4K @ 60fps preferred)
- Clean camera lens—dust/dirt reduces detection accuracy
- Ensure camera feed is connected to Adrenaline (check Race Control camera panel)
Stopwatch Timing: Crossings in Wrong Order
Symptoms: Rider 5 crossed before Rider 3, but recorded opposite
Solutions:
- Use Crossing Order Editor to fix: swap crossings, adjust timestamps
- Delete incorrect crossing and re-add with correct rider number
- For future: use "Look Free" mode (Alt+Enter gate drop, Spacebar crossings in real-time)
- Slow down—wait to see number before hitting Spacebar
Race Won't Start (Riders Can't Join)
Symptoms: Riders say race not showing in app
Solutions:
- Check race status: must be "Staging" or "Live" (not "Scheduled" or "Complete")
- Ensure riders registered for that specific race/class
- Verify riders have internet connection to receive race updates
- Try "Refresh" in app or restart app
- Check event is published (not draft)
Event Setup & Management Issues
Can't Add Classes to Event
Symptoms: "Add Class" button missing or not working
Solutions:
- Ensure you're in event editing mode (not viewing published event)
- Check permissions: you must be event owner or have edit rights
- Try creating from class template instead of manual class creation
- Clear browser cache and refresh
Event Not Showing in Public Listing
Symptoms: Created event but no one can find it
Solutions:
- Publish the event (draft events are private)
- Set visibility to "Public" (not "Private" or "Unlisted")
- Ensure event date is in the future (past events don't show in default listing)
- Wait up to 5 minutes for cache to refresh
Can't Edit Published Event
Symptoms: Fields are read-only or greyed out
Solutions:
- Click "Edit Event" button if viewing published version
- Some fields locked after registration opens (e.g., class structure)—this is intentional
- To make major changes: create new event and migrate registrations, or contact support
Ordering/Grouping Not Saving
Symptoms: Drag-and-drop changes revert after refresh
Solutions:
- Wait for "Saving..." indicator to complete before leaving page
- Check internet connection—changes saved to server
- If using "Group Classes" or "Order Races," ensure you click "Apply" or "Save"
- Try refreshing page and re-ordering—might be browser caching issue
Track Development Issues
TrackLang Errors: "No matching tracks detected"
Symptoms: Error when clicking "Run"
Solutions:
- Ensure you have
track trackname { ... }declaration - Check track key matches in feature locators (e.g.,
mx1@100if track istrack mx1) - Verify opening and closing braces match
TrackLang: "Circular reference" Error
Symptoms: Error like "Circular reference: turn1 → turn2 → turn1"
Solutions:
- Feature A's location depends on Feature B, but Feature B depends on Feature A—infinite loop
- Use absolute positioning (
@100) for one of the features instead of relative (@featurekey+50) - Review feature location chain to find the loop
3D View Not Updating After Code Changes
Symptoms: Changed code but 3D view still shows old track
Solutions:
- Click "Run" to rebuild the track—changes don't apply until you run
- Check console for errors—failed builds don't update 3D view
- Refresh browser if 3D view frozen
Can't Fork Public Track
Symptoms: "Fork" button missing or greyed out
Solutions:
- Track must be marked "Public"—private tracks can't be forked by others
- You must be logged in to fork
- Can only fork minor versions (not build versions)
Rider Profile & Account Issues
Profile URL Not Working (404 Error)
Symptoms: adrenaline.mx/racer/123/doe/john shows "Not Found"
Solutions:
- Profile URL format:
/racer/[number]/[last]/[first]- check spelling and number - Rider may have changed profile URL—search by name instead
- Rider may have deleted account or set profile to private
- Try searching from main rider directory instead of direct URL
Sponsor Logos Not Showing
Symptoms: Uploaded sponsors but they don't display
Solutions:
- Sponsor display requires "Rated Account" subscription—check subscription status
- Uploaded image must be valid format (PNG, JPG, SVG)
- Image might be processing—wait a few minutes and refresh
- Check image size: max 5MB per logo
Ratings Not Updating After Race
Symptoms: Finished race but Elo rating unchanged
Solutions:
- Only sanctioned races affect ratings—check if event was sanctioned
- Race must be marked "Complete" with final results published
- Ratings update within 24 hours (not instant)
- Must have raced against other rated riders (can't gain rating racing alone)
Can't Add Machine to Profile
Symptoms: Add machine form not saving
Solutions:
- Fill all required fields: year, make, model, number plate
- Number plate must be unique to your account (can't duplicate your own numbers)
- Check internet connection
- Try from profile management page instead of registration flow
Performance & Connection Issues
Page Loading Slowly or Timing Out
Solutions:
- Check internet connection speed
- Clear browser cache: Ctrl+Shift+Delete → Clear cached files
- Try different browser (Chrome/Edge recommended)
- Disable browser extensions that might interfere (ad blockers, etc.)
- If on mobile: close other apps to free memory
"Connection Lost" During Race
Symptoms: Race Control shows connection error
Solutions:
- Check WiFi/cellular connection
- Page will auto-reconnect when connection restored
- Data is cached locally—crossings/results won't be lost
- Refresh page if auto-reconnect fails
- For critical races: use wired ethernet connection instead of WiFi
Changes Not Saving (Generic)
Symptoms: Made changes but they revert after refresh
Solutions:
- Wait for "Saving..." indicator to complete
- Check browser console for errors (F12)
- Verify internet connection active
- Clear browser cache and try again
- Try incognito/private browsing mode to rule out extensions
Mobile App Issues
Location Services Not Working in App
Solutions:
- Check phone location services enabled (Settings → Location)
- Grant Adrenaline location permission (Settings → Apps → Adrenaline → Permissions)
- Enable "High Accuracy" mode (not battery saver)
- Ensure phone has clear view of sky for best accuracy
- Restart app and phone if issue persists
App Crashes During Race
Solutions:
- Update to latest app version from app store
- Close other apps to free memory
- Restart phone before race
- Ensure phone battery above 20% (low battery can cause instability)
- Report crash to support with phone model and OS version
Can't See Live Results in App
Solutions:
- Pull down to refresh results screen
- Check internet connection (cellular or WiFi)
- Ensure race is "Live" status (not "Scheduled" or "Complete")
- Log out and back in to refresh session
General Troubleshooting Steps
When All Else Fails:
- Clear cache: Ctrl+Shift+Delete → Clear browsing data (last hour or last 24 hours)
- Try incognito: Open incognito/private window—if it works there, it's a cache/extension issue
- Different browser: Try Chrome, Edge, Firefox, Safari—helps isolate browser-specific bugs
- Different device: Try phone, tablet, or different computer—helps isolate device issues
- Check status: Visit status.adrenaline.mx for known outages or maintenance
- Update browser: Ensure you're on latest browser version
- Restart device: Sometimes the old "turn it off and on again" actually works
Still Need Help?
Contact Support
If you've tried the solutions above and still have issues, we're here to help!
- Contact: Submit a support request
- Include: Description of issue, steps to reproduce, browser/device info, screenshots if helpful
- Response time: Usually within 24 hours (faster during events)
When Reporting Issues:
Help us help you faster by including:
- What you were trying to do
- What you expected to happen
- What actually happened (error messages, unexpected behavior)
- Steps to reproduce the issue
- Browser and version (e.g., "Chrome 120 on Windows 11")
- Screenshots or screen recording (if applicable)
- Event ID or race ID (if issue is event-specific)
Related Topics
- Getting Started - New to Adrenaline?
- Frequently Asked Questions - Common questions answered
- Manual Timing - Stopwatch timing guide
- Online Registration - Setting up registration
Was this information useful?
Help us improve our documentation by rating this article and sharing your feedback.