Official source

Quick answer

[Official] Make sure every device has the correct system date and time, preferably with automatic time synchronization enabled. A significant clock difference can prevent both joining and hosting. Then wait until the host is fully loaded into the world, check that the host has no connection warning, confirm that every device is online, and fully close and reopen Big Walk before retrying.

Official source

Start with the system clock

  1. Open the date and time settings on every device in the group.
  2. Enable automatic date, time, and time-zone settings where available, then trigger a manual sync if the platform offers one.
  3. Fully close Big Walk after correcting the clock, reopen it, and create a fresh host session.
  4. Retry from the active friend-game listing or use the new Join Code from that session.
Official source

Retry a clean active session

  1. Have the host start the session and wait until their character is loaded into the world.
  2. Check the host's lower-left corner for a connection warning and resolve the host's internet problem before guests retry.
  3. Confirm that each joining device can reach other online services.
  4. Fully quit and reopen Big Walk on the joining device, then retry the active friend game or current Join Code.
  5. If that fails, fully quit and reopen Big Walk on the host device, start a new session, wait until the host is in the world, and retry.
Official source

Check the Join Code and version

[Official] Big Walk generates a new Join Code each time the host starts a session, so use the code shown for the current session. Version numbers have three parts: the first two must match between players, while the third may differ.

Official source

If players join but the session freezes

[Official] Jittery players, dropped voice, or a frozen session point to a network or bandwidth problem rather than the initial join check. Stop network-heavy programs, reduce other heavy traffic, move closer to Wi-Fi or use Ethernet, and check whether the host is running at a stable frame rate. If every player is affected, lower the host's graphics quality or test a different host.

Community report

What current player reports show

[Corroborated community evidence] Two separate launch-week Reddit discussions include players who reported that correcting or synchronizing the device clock resolved their connection failure. That matches the official FAQ and makes the clock check the best first step.

[Community-reported] A separate August 10 discussion describes groups still unable to assemble a session after changing hosts and restarting. The official checklist is therefore a diagnostic sequence, not a guaranteed fix for every timeout. If it still fails, report the platform, displayed version, host platform, clock status, and exact error to help@bigwalk.game.