There is at least one user report about the device receiving 403 errors when trying to download, likely caused by the download link expiring. It can expire because the client will not ask for a new link if it gets interrupted during download (has to resume), and there are state scripts that may be designed to delay the update. It is possible to adjust the client to handle more of these cases but this is a lot more effort and would not cover 3rd party clients.
Right now it is set to one hour, unless there are any problems we should consider increasing to 24 hours, as most these cases would be resolved in such a long time window. I believe we shortened this time in the past, before we were aware of the resume & state script issues. We could probably use that change/PR as a reference to change it again.
There is at least one user report about the device receiving 403 errors when trying to download, likely caused by the download link expiring.
It can expire because the client will not ask for a new link if it gets interrupted during download (has to resume), and there are state scripts that may be designed to delay the update.
It is possible to adjust the client to handle more of these cases but this is a lot more effort and would not cover 3rd party clients.
Right now it is set to one hour, unless there are any problems we should consider increasing to 24 hours, as most these cases would be resolved in such a long time window.
I believe we shortened this time in the past, before we were aware of the resume & state script issues. We could probably use that change/PR as a reference to change it again.
Acceptance criteria
Download link is valid for 24 hours