Diagnostics & Troubleshooting
Resolve connection issues and interpret the Companion's API diagnostics.
Use the connection screen for transport problems and Diagnostics for suspicious or incomplete data returned by the Local API.
Companion cannot connect
- Confirm that Uptime is running and the intended simulation is loaded.
- Confirm that the game's Local API is enabled.
- Check protocol, hostname, and port on the connection screen.
- Select Retry after the game becomes available.
- Review Latest result and the recent connection try log.
The normal same-computer endpoint is http://127.0.0.1:9875. A different machine, port, or network
setup requires the endpoint exposed by that game instance.
Diagnostics
Diagnostics scans the current API snapshot and groups suspicious entries by severity and source. The summary shows counts for Critical, Errors, Warnings, and Groups.
Search or filter the table, then open a group to inspect its paths, fields, and findings. Select Refresh after the game state changes or after reconnecting.
Diagnostics is primarily evidence about the data the Companion received. A warning can explain why a view is incomplete, but it is not automatically an in-game incident.
Common checks
- Old values remain visible: the Companion may be reconnecting and retaining the previous state.
- A table looks incomplete: clear search and filters, reveal hidden columns, or reset its view.
- A search operator is treated literally: enable Advanced search in Settings.
- Resolved incidents disappear too quickly: increase Resolved history retention.
- A map looks wrong: use Fit map or Rearrange, then verify the physical topology in Uptime.
If the issue persists, use Report a Bug in the Companion sidebar and include the game version, endpoint context, reproduction steps, and relevant diagnostic finding.