A ROB RUN waiting for status information screen tells you where the attempt appears stuck, but not necessarily why. The useful next step is to narrow the evidence without making a risky change to your server progress or installing an unofficial repair tool.
The official Help Center provides general loading, file and connection checks. Those documented checks are relevant here, while the specific message is treated as a symptom rather than a diagnosis confirmed by Kefir.
Capture the symptom before changing anything
Write down the exact wording and whether it appears before server selection, after an invitation or during another step you can describe. Note whether the game remains responsive and whether any separate code or dialog appears. These distinctions help separate a connection attempt from a frozen application.
A screenshot is useful if it includes the relevant message without unrelated personal details. Keep the original result before a retry so you can tell whether the next attempt actually changed anything. Avoid describing every long load as the same error.
Check official notices for the relevant service
Use the official server-notice links and look for a statement that fits your region or symptom. If matching maintenance is announced, follow the developer’s direction rather than repeatedly changing your computer to compensate for work outside it.
If there is no relevant notice, do not jump to the opposite certainty that every server is healthy. Continue with the local checks and describe the state as unconfirmed. A player-count graph and a handful of unrelated comments are not substitutes for evidence about your attempt.
| Evidence | Useful interpretation |
|---|---|
| Official notice matches your server | Follow its scope and instructions. |
| No matching notice | Continue checking; the cause remains unconfirmed. |
| A named error code appears | Use that code’s specific official explanation. |
| The application crashes | Follow the crash branch rather than only connection advice. |
Complete updates and do a controlled restart
Close the game, check Steam for pending updates and allow installation to finish. Then restart Steam and launch the game again through the library. This follows the general direction of Kefir’s loading guidance and helps distinguish an old client state from a persistent symptom.
Record the result of that one retry. If the same screen returns, keep the wording and move to the next check instead of repeating the same action indefinitely. Do not attach a guaranteed waiting time to a symptom whose cause has not been established.
- Close the current game attempt.
- Check for pending Steam or game updates.
- Let the installation complete rather than launching during it.
- Restart Steam, launch through the library and attempt the same connection.
- Compare the new result with the screenshot you recorded.
Check the connection you are actually using
Confirm that normal websites load. If you are using a guest network, complete any legitimate sign-in page and check whether that network permits the connection you need. A working web browser does not prove every game connection works, but a failed ordinary connection is a useful clue.
Avoid changing several network settings at once. If you compare another trusted connection, record which network you used and whether the symptom changed. This is a diagnostic comparison, not proof that a named provider or router model is always the cause.
Verify game files before a full reinstall
In Steam, use the game’s Properties, then Installed Files, then Verify integrity of game files. Let the process complete before starting a fresh attempt. If a repair or update is required, finish it before deciding whether the symptom persists.
A full reinstall is not the first documented step for every loading problem. Keep the process ordered so that you can explain which check was performed and what it found. If the program crashes or reports a code during the next attempt, switch to startup troubleshooting or the code reference as appropriate.
Escalate with a precise report
Send Kefir the exact message, the point in the process, server or region information if available, steps already tried and an approximate incident time. Include a screenshot or short video that shows the symptom. If the issue concerns your character, use the UID through the official support route.
Do not use Surrender to Feds just because someone described it as a workaround. That route has game-progression implications and is documented for synchronizing friends on different servers. It does not establish a universal fix for this loading message.
Waiting for Status Information FAQ
01Does this message always mean the servers are down?
No confirmed cause is established here from the wording alone. Check a matching official notice and any additional error before deciding.
02How long should I wait on the screen?
There is no verified universal duration for this symptom in the official references used here. Record whether anything changes and follow the controlled checks rather than a guessed timer.
03Should I reinstall immediately?
Start with the official restart, update and file-verification sequence. A reinstall should not replace identifying the symptom and preserving useful evidence.
04Can joining another server solve it?
Do not assume so. The official transfer route is a game action with consequences, not a generic connection reset. Diagnose the message first.
Sources & useful references
Game rules below are linked to their official references. Tactical suggestions in this guide are practical advice, and do not promise a particular payout or outcome.