connecton satus mobil profile

README.md

@@ -853,3 +853,7 @@ Open **Settings > Decoder / socket diagnostics** to inspect Main, Split, Pit ent
 Use the AMMC host IP in WebSocket URLs (for example `ws://192.168.1.75:9000`), not the physical decoder IP. Give each AMMC channel its own port; enable only installed channels. `127.0.0.1` means the computer running the browser.
 
 Frames include all received WebSocket messages; PASSING counts recognized passing messages, not accepted laps. Handled includes split/pit events and start references. Ignored, invalid laps and JSON errors are separate. Select a channel to inspect its latest raw frame and 50 diagnostic events. Pause freezes only this display; Clear resets only that channel's diagnostic counters/log, preserving connection timestamps. Copy provides a manual fallback on plain HTTP. Diagnostics are local to this browser, memory-only, capped at 512 characters per sample, and reset on page reload. They neither change timing nor expose a new public API. Logs may contain transponder numbers; review before sharing.
+
+### Mobile Profile Connection Status
+
+The personal training link displays the last successful data retrieval. After 30 seconds without applying fresh data, it warns that statistics may be outdated (including when updates are deferred during input). A failed request keeps existing statistics and shows **Retry**. Finish any active input before retrying. Requests time out after 15 seconds; automatic polling continues every 10 seconds while the page is visible, without overlapping requests. The status describes profile retrieval, not decoder connectivity or confirmation that a car-change marker was saved.