Read the state before tapping repeatedly
If the screen says the run is held, the forest has paused its movement in the current page. The next play input resumes it. That first input is used only to continue; it does not also change the companion’s curve.
If you see the ready screen or a result screen instead, you are looking at a different state. Check the visible wording before assuming controls are unresponsive. A menu or share dialog can also block gameplay input until it is closed.
Separate an open page from a saved game
ORBIT keeps an active run’s position in memory. Its local saves hold records, accumulated progress and preferences; they are not a snapshot of every live frame. A reload creates a new page session even if the browser still shows the same URL.
This is why reopening after the browser has discarded or closed a page can bring back your discoveries without bringing back the exact branch you were approaching. A preserved best does not imply that an unfinished attempt was saved for later continuation.
Investigate unexpected restarts
If a run unexpectedly returns to the ready screen, note whether you reloaded, closed the tab, reopened an installed app or returned after a long absence. Those details distinguish game hold behavior from the browser ending the page session.
For short interruptions, leave the game open and use the visible resume prompt when you return. For important records, finish the attempt before making browser changes. Report a restart with the device, browser and sequence of actions; avoid describing every return to the game as the same kind of resume problem.