Hi, We're using addressables to download remote assets for a mobile title following an initial install containing minimal data. At this time, there is no local cached version of the files requested. The user may have no active connection when they launch the title, in which case we respond to the "failed" state of the asset-load from the addressable system and prompt the user to connect to the internet and try again. The issue we're seeing is that there doesn't seem to be any way currently to prompt the addressables system to manually retry the load operation. There are settings for a fixed number of retries in sequence following a request's failure, but this is not the same as requesting a retry in response to a user-event. Once the task-load operation has failed for the requested asset, the operation sits sat in the failed state forever. Subsequent calls to LoadAssetAsync do not prompt another load attempt, as the addressables system sees the original failed operation for the asset and so early-outs. We can clear the load operation explicitly with the operation handle, but it appears the dependent operation that actually invokes the web-request is cached in its failed state, and we have no access to that to reset it. Any advice with this matter would be greatly appreciated, as the flow we're using is very common for mobile titles, so I wonder whether I'm just missing something obvious. Thanks!