I like to discover games with Steam Discovery Queue. However, I have been encountering an error for several years, I am not the only one in this situation, and I have not found any fix yet.
Let us say I have finished discovering a set of 12 games and want to discover another set of 12 games. Then I have to click on Start another Queue
. At this point, either the process goes fine, or I encounter the following error:
There was a problem saving your preferences. Please try again later.
When I click OK
and then reload the page, after around 6 seconds, another error message appears:
An error was encountered while processing your request:
Failed to load queue
Here is a video recorded by a Steam user of the process described above:
The error message Failed to load queue
can also appear as soon as I click on Click here to begin exploring your queue
. When this is going to happen, there is no background game banners visible behind the brown rubber band.
It might be relevant to mention that there exist preferences for Steam Discovery Queue at this webpage:
After I refresh the Steam Discovery page, or go to a page on the Steam store, or visit a profile on Steam community, the issue sometimes disappears. Sometimes, if I manage to modify my preferences for Steam Discovery, the error disappears. Sometimes, I just give up and the issue disappears when I try again a few hours later.
I believe this error mostly happens to people who have already discovered thousands of games. It seems the error also occurs for some users during major sales, and could be linked to Steam network being overloaded.
Best Answer
The cause is, like you proffered, in all probability a server overload.
As comments here and in other relevant threads suggest, this occurs more frequently during sales and other large events: in the Steam Community thread you linked, most users complain about not being able to get event trading cards.
This same overload - it seems - can also
Error code: -330. Failed to load web page (unknown error)
).I think (and I have little knowledge about these matters) the reason this tends to happen right after finishing a queue, is that these queues are fully preloaded in advance. This is substantiated by the fact that if you deviate from the queue and continue later, it will let you pick up where you left it.
Moreover, this would also explain it happening generally to users with a higher discovery count (since, I guess, it will take longer to parse the database).
An interesting comment in that same thread sheds some more light on a possible underlying complication:
As for circumventing this problem:
A better question would be why this is still happening. In anticipation, and answering your main question directly: yes, but only Valve can fix this.