Single post in New request timeout handler
Forum Index > Core > Announcements > New request timeout handler >
Some users have been seeing issues with the game getting "stuck". Thanks to this bug report, I have made an adjustment.
For some reason, the requests will fail to connect to the server, but rather than detecting this properly and going through normal error handling routines, it just... gets stuck.
I have no idea why this happens nor how to fix it, but it was discovered that forcing it to stop (via turning wifi off and on again!) at least got the page un-stuck, as it allowed the error handler to work.
To implement this "on purpose", I have added a timeout to requests. If you had this issue, you may now start seeing a "Request Timeout" message, asking if you would like to retry the request.
This is important because PFQ does not have the structure in place for "idempotency" -- I cannot simply have it retry automatically, because it may lead to duplicate purchases or other actions. This is why it will remain a manual "do you want to retry?" query. I may be able to cut this down in future by making a list of "safe to retry" things, but for now... manual.
I hope this doesn't cause too much trouble, and in fact helps those who were unknowingly facing the error before.