Error code 59 in Valorant occurs during login, when the client fails while fetching its token from Riot's login queue (the error is sometimes referenced internally as a login queue failure). In practice it behaves like its sibling code 43: a connection between the client, Vanguard, and Riot's services did not complete. Riot's remedy pattern applies: full client restart, Vanguard check, then network.
vgc): start it if stopped and set Startup type to Automatic. A down Vanguard blocks the login flow that 59 reports.ipconfig /flushdns, and firewall/antivirus allowances for the Riot Client and Valorant.%localappdata%\Riot Games, then sign in fresh.Both codes are connection failures at the platform door, but 59 happens a step earlier in the sequence, while the client is being admitted through the login queue, which is why it often appears at busy times or right after patches when queues are active. Corrupted saved credentials also surface here, because the queue token step is where the client presents them.
It only happens right after a patch. Coincidence? Probably not. Patch launches combine fresh client code, long login queues, and heavy load, the exact conditions for 59. Waiting an hour and restarting the client resolves most patch-day cases.
Repairing the game files did not help. Why? Error 59 is not about game files; it is about admission to the platform. File repairs fix content errors, while 59 lives in the client, Vanguard, and network path, which is where its fixes concentrate.