
WARDOGS Beta Access: Pre-Order or Request an Invite
Compare guaranteed WARDOGS Closed Beta 02 access with limited Steam invite waves, then check what confirms entry and how long the session lasts.
Open report
Field report · technical support
Work out whether WARDOGS access is missing, the test is unavailable or login failed after the queue. Follow the matching checks and preserve the error.
Triage brief
An August 21 Steam report describes Access Denied after the login queue even though the player had pre-ordered and received a Playtest invitation. The message alone therefore does not establish that an account lacks access. EVIDENCE / 01Original Steam report: pre-purchased but access denied, August 21Open source (opens in a new tab)
Diagnose in this order
Editorial guidance
Check the announced beta dates and ending time. An old installation is not proof that a new session is available. Valve documents separate Playtest access and playable states, including the ability for a developer to deactivate a test. EVIDENCE / 02Valve: Steam Playtest access and playable statesOpen source (opens in a new tab)
Within the scheduled window, choose a check based on how far you get.
| Where you are stopped | Next check |
|---|---|
| No Playtest entry in the library | Confirm the account and whether access was actually granted. Use the beta access guide. |
| The entry exists but installation or an update is incomplete | Finish preparing that client; use the Playtest guide for local installation checks. |
| The game opens and refuses login | Capture the whole message and look for a current notice about login or access. |
| You enter a queue, then receive Access Denied | Note the time and queue stage; a library check alone will not explain this failure. |
| You can join, but the application then closes | Treat the closing application as a crash and preserve any crash message. |
An invitation request and an accepted invitation are different states. For Closed Beta 02, BULKHEAD advertises a pre-order guarantee and limited invitation waves. EVIDENCE / 03BULKHEAD: Closed Beta 02 scale-test announcementOpen source (opens in a new tab)
Check which account received the purchase or invitation before changing the installation. If you have a grant but cannot see the test, fully close and reopen Steam, then check again. If the entry remains absent, preserve the grant details for support.
If you only requested an invitation, return to the access guide. Reinstalling the commercial game does not provide evidence that your request was accepted.
This is the distinction preserved by the August report: the player reached repeated login queues before being denied. That sequence is useful when describing a failure, but an August incident cannot tell you whether September's service is currently down. EVIDENCE / 01Original Steam report: pre-purchased but access denied, August 21Open source (opens in a new tab)
Look for a notice covering the time and client you are using. Check the date of any quoted update. A screenshot shared without its date, or a post saying “resolved,” may describe a previous test.
If your message includes 1147405308, use the code-specific evidence page. Preserve other codes exactly as shown; similar wording does not establish that two numbers mean the same thing.
Team17's support page provides a general support portal for games without a listed product entry. EVIDENCE / 04Team17 Player SupportOpen source (opens in a new tab)
In a private request, include your access route, whether the Playtest appears in the library, the last screen reached, the complete error and the attempt time with a timezone. Include purchase or invitation details only when requested through the official support process.
If a current official notice describes a matching incident, follow that notice and keep your report for a failure that persists afterward. Avoid deleting user data or making Windows security changes in response to an access message with no local cause identified.