Skip to guide content
Random Addingby Melirate

Live Race

Reconnect to a Live Race

Return to the same race before its shared deadline and restore saved answers without restarting the clock.

Available locallyJourney guide

Before you start

  • The race must still be running, and the current browser profile must have saved the active attempt. The original deadline continues while disconnected.

Steps

  1. Return to the same room

    Refresh or reopen the existing race invite on the local review server. Do not create a new room to replace an in-progress race.

    Open the Live Race: active player and late spectator guide

  2. Let the room state load

    If the same participant's race is still running and the deadline has not passed, the app can resume the same attempt and reapply its saved answer prefix.

    Open the Live Race: active player and late spectator guide

  3. Continue before the deadline

    Answer what remains. The timer reflects the original shared deadline; refresh and disconnect do not grant extra time.

    Open the Gameplay: timer expiry and background tab guide

  4. If the deadline passed

    Return to the room and wait for finalization. A late joiner becomes a spectator; an expired or cancelled race cannot be resumed as a new attempt.

    Open the Live Race: provisional result guide

What to expect

  • A restored attempt keeps the original attempt ID, deadline, and previously submitted answer events.
  • If local in-progress storage was unavailable, the app warns that answers could not be saved.

Other paths

Visual guide

Recorded walkthrough

Walkthrough recording · 40 sec

These are silent local synthetic preview captures. Account clips and screenshots show the unconfigured guest preview, not the locally prepared member flow. Some demos use 5-, 15-, or 20-second timers; private invitation details are hidden. If playback is unavailable, use the captions when present or read the full transcript below.

Read the full recording transcript

Synthetic local review: the 15-second race timer is shortened for this capture.

The host and returning racer both mark ready, then the host starts one shared race.

Two answers are saved in the current attempt before the page refreshes.

The page restores the same attempt ID, two-answer prefix and original deadline; refresh adds no time.

The host browser disconnects. The connected racer keeps the original shared clock and continues answering.

The room accepts the guest’s score and finalizes without the host. The disconnected host has no submission.

This capture is a local review preview with synthetic players.

Annotated screens

Each numbered note names the control or state marked on the screen.

Actual active player gameplay with a synthetic accepted-answer prefix and the game’s real numeric keypad. Numbered arrows identify Leave, the answer field, and every keypad option.View full-size original annotated screen (new tab)
Annotated Random Adding screen.

What the numbered markers show

Actual joined racer gameplay showing a saved synthetic score prefix and the real answer controls.View full-size original annotated screen (new tab)
Additional annotated screen state.

What the numbered markers show

Actual late-join spectator state: the observer can watch this race and play in the next one; private invite details stay masked.View full-size original annotated screen (new tab)
Additional annotated screen state.

What the numbered markers show

Actual game after refresh: the same two-answer score prefix, attempt ticket and original shared deadline are restored.View full-size original annotated screen (new tab)
Additional annotated screen state.

What the numbered markers show

Actual Leave race view confirmation with both choices and the real close control numbered.View full-size original annotated screen (new tab)
Additional annotated screen state.

What the numbered markers show

Actual room view after confirmed Leave: the room says the shared clock kept running and offers Return to race before the deadline.View full-size original annotated screen (new tab)
Additional annotated screen state.

What the numbered markers show

Actual gameplay after Return to race: the original one-answer prefix and original race clock continue.View full-size original annotated screen (new tab)
Additional annotated screen state.

What the numbered markers show

Actual results view displayed when the real solo timer expires. This screenshot shows the expiry result; it does not simulate a device background scheduler.View full-size original annotated screen (new tab)
Annotated Random Adding screen.

What the numbered markers show

Actual accepted result while the shared deadline has passed and the room is still in its finalization grace period.View full-size original annotated screen (new tab)
Annotated Random Adding screen.

What the numbered markers show

Actual pending result after a controlled local request failure. The score remains visible while sync is waiting.View full-size original annotated screen (new tab)
Additional annotated screen state.

What the numbered markers show

Actual pending local result after the same request retries successfully and receives a room acceptance receipt.View full-size original annotated screen (new tab)
Additional annotated screen state.

What the numbered markers show