Why reconnecting matters
An offline copy can only use files already available on the device. ORBIT’s production service worker serves its cached release and checks for an updated worker when the game is opened online. A working old copy is therefore not proof that you already have the latest release.
Leave the game connected long enough for a new offline shell to download. If the connection fails during preparation, repeatedly reopening without connectivity cannot retrieve the missing release files. Return to a stable connection and try again.
Allow the old session to finish
ORBIT’s update design waits for old game windows to close instead of replacing a running session immediately. Finish your current attempt, then close the game’s tabs and installed windows. If you are using Float, return it to its original tab and close that game tab too.
Open ORBIT again while online. This provides a clean opportunity for the prepared release to become active. A single reload while another old game window remains open may not accomplish the same thing, so check for forgotten tabs when an update seems delayed.
Separate updates from saved records
The release cache and local game progress serve different purposes. Routine offline-cache replacement is designed to remove older cached files; it is not a command to erase your best scores or discoveries. There is no need to clear all website data as a normal update step.
A release can change gameplay rules or record categories, so examine the selected companion and course if a displayed best changes. When reporting an update issue, include the game address, browser and the behavior you still see after closing old windows and reopening online.