Journey JNY-285013

• 08:42:12Vehicle StartedDriver started the vehicleUI: Cockpit boot sequence, MG splashCockpit boot completedCockpit PlatformBoot duration 6.2 s · SoC load 42% · Software v4.8.2
• 08:42:18Home ScreenHome screen presented to driverUI: Home widgets renderedHMI compositor readyHMI RuntimeRender latency 184 ms · Frame drops 0
• 08:42:26Navigation OpenedDriver tapped NavigationUI: Map view with last destinationNavigation service attachedNavigation ServiceMap tile load 412 ms · GNSS fix 3D, 9 sats
• 08:42:31Search InitiatedDriver opened destination searchUI: Search overlay with keyboardSearch API session openedSearch APIResponse time 268 ms · Result count 12
• 08:42:36POI SelectedDriver selected POI 'Kings Cross Station'UI: POI preview cardPOI resolved from search indexSearch APIResponse time 311 ms · Cache miss
• 08:42:42Route RequestDriver requested routeUI: Calculating route spinnerRoute calculation request dispatchedRoute APIRequest id rt-4f21a8 · Payload 2.4 KB
• 08:42:48API TimeoutDriver waitingUI: Spinner still displayed, no feedbackRoute API request timed outErrorRoute APILatency 6,004 ms · Status 504 · Retry policy 1 automaticERR_ROUTE_TIMEOUT (gateway 6000 ms exceeded)
• 08:42:51RetryDriver tapped retryUI: Spinner restartedRoute calculation retriedRoute APIAttempt 2 of 2 · Backoff 0 ms
• 08:42:58API TimeoutDriver waitingUI: Spinner, then generic error toastRoute API request timed outErrorRoute APILatency 6,011 ms · Status 504 · Upstream route-eu-w3ERR_ROUTE_TIMEOUT (gateway 6000 ms exceeded)
• 08:43:04User AbandonedDriver exited navigation without a routeUI: Returned to home screenNavigation session closed, no route activeNavigation ServiceJourney duration 4m 21s · Friction score 92 / 100

The driver opened Navigation 14 seconds after startup and selected a destination without difficulty. The route request was dispatched to the Route API, which exceeded its 6,000 ms gateway budget twice. No actionable feedback was displayed during either wait, and the driver exited navigation without a route after 4m 21s. This journey matches the Navigation API Timeout Spike anomaly associated with release v4.8.2.