WARDOGS error 1628505084

What the dialog says, in two transcriptions

Two players have written the dialog out, and they do not quite agree. On launch day, 10 September, one transcribed it with its buttons: “Could not retrieve the latest game data from the game data service. Please try again shortly. (Quit Game) (Retry)”. On 12 September another gave it as “Unable to retrieve the latest game data from the game data service. Please try again shortly.” The difference is one word at the front, and it is worth noticing for the same reason it mattered on the 1628505091 page: nobody is quoting the client from a screenshot, and BULKHEAD and Team17 have printed neither version. What the two agree on is the title — GAME DATA UNAVAILABLE — the code, the phrase “game data service”, and that the dialog offers a retry.

The sequence one report describes

The 12 September thread is the only dated report that puts the string in order with what came before it. The player was in a normal match, was “suddenly removed from the match” with the message “You have been removed from the match”, tried to continue or reconnect, and got this dialog. They add that it had happened more than once and that, previously, restarting the game had cleared it — and that this time the same sequence repeated. That is one player's account of one machine. It is recorded here because it is the only description of the string that says anything about when it appears, and because it is consistent with the dialog's own text: the client is asking a service for data and not getting it. Whether the removal and the failed fetch share a cause is not something the report can establish, and it does not claim to.

• String: “Game Data Unavailable”, error code 1628505084, per both threads
• First dated public report: 10 September 2026, 11:38 PDT
• Reported context, 12 Sep: removed from a match, then the dialog on reconnecting
• Player-reported, unconfirmed: restarting the game cleared it on earlier occasions, not on the reported one
• Cause: not published by anyone

Not a queue, not a timeout, not the anti-cheat

The code sits one digit from 1628505085 and seven from 1628505091, and searches for it return threads about both. They are different failures. 1628505085 is an access-denied string from the authentication family, reported during the closed beta. 1628505091 is a join timeout — nothing admitted you and nothing refused you. This one arrives with its own dialog and a Retry button, and the one contextual report places it after a match rather than before one. If your screen says you are in a queue, or that a server refused you, or that the timeout period expired, those are other pages. If it says GAME DATA UNAVAILABLE with this code and a Retry button, you are on the right one.

1628505091 — the timeout seven digits away →

What nobody has published, and what this page will not borrow

No BULKHEAD or Team17 text checked for this section prints a numeric WARDOGS error code, and a search of every post on the Steam news feed for this one, and for the phrase “game data unavailable”, returns nothing. Four fix videos were published in the week after launch with the code in their titles; they are the reason a reader may have arrived here from a search, and they are deliberately not cited, because a channel that titles a video with an error string has demonstrated that people are searching for it and nothing else. There is no official cause, no official fix, and no numbered step list here. The one thing the record supports is what the dialog itself says: try again shortly.

Connection failures by symptom, when you have no string →

Common questions