Sometimes, the DOWNLOAD operation can end up in the ERROR state not because the file could not be downloaded by the data provider, but because the failure of some post-processing operations that are performed on the file (e.g. the reading of the file by SNAP, for the Sentinel products).
In that case, the product is not shown in the workspace, even if the corresponding file is present on the server, in the folder of the workspace.
To save some space on the servers, we could add a flag in the wasdiConfig so that, when the flag is set to true, we will proceed to the deletion of the downloaded file on the server, when the overall DONWLOAD operation ends up in ERROR.
Sometimes, the DOWNLOAD operation can end up in the ERROR state not because the file could not be downloaded by the data provider, but because the failure of some post-processing operations that are performed on the file (e.g. the reading of the file by SNAP, for the Sentinel products).
In that case, the product is not shown in the workspace, even if the corresponding file is present on the server, in the folder of the workspace.
To save some space on the servers, we could add a flag in the wasdiConfig so that, when the flag is set to true, we will proceed to the deletion of the downloaded file on the server, when the overall DONWLOAD operation ends up in ERROR.