Throughout yesterday and today our team has been experiencing issues with our game’s systems being loaded through InsertService:LoadAsset in an outdated version. This seems to happen randomly and inconsistently on the same place when loading models of the same AssetID. We’ve had this happen on two separate models used for the same game. We started encountering this issue just before yesterday’s service outage began.
The results of my testing are shown in the image below. One of the differences between the current and outdated versions of the model being tested was that one of our scripts had an adjusted data table for a game pass. The up-to-date version has the Title string of the pass being “Starter Pack!”, whereas the outdated version had “Starter Bundle!!” The code running this test is checking the data table for the title of this game pass to see if it’s correct, and after running this test multiple times, an outdated version of the asset was loaded between 20-40% of the time.
Despite this, forcefully loading the asset through InsertService:LoadAssetVersion with its most recent version ID does seem to be working correctly and we’re using that as a workaround for now.
This issue is quite disruptive for us as our team has been trying to test new features and will randomly get loaded into a server with outdated systems. In addition, as we’re not sure if it’s all of our models or just the ones used for our dev server, publishing to the live game could risk our players experiencing major disruptions and data issues due to an outdated version of our game systems being loaded in live servers.
Expected behavior
InsertService:LoadAsset should be consistently loading the most up-to-date version of an asset and not outdated versions
A private message is associated with this bug report
