Saved export path in Discovery Tool 3.1.1 does not persist

Issue Summary

Saved export path in Discovery Tool 3.1.1 does not persist. After a day or more, the path becomes empty and results in zip files not being transferred to the expected location.

Steps to Reproduce

1. Set up Insight Discovery 3.1.3 and the Discovery Tool 3.1.1.
2. Configure the Export with FileCopy method as per this guide. This could also affect any other export type.
3. Test with a manual scan and verify that the scan result (zip file) is exported to the saved path as expected.
4. After a day or two, run a scan again and check if the scan result is exported to the saved path like it did.
5. Check the Export settings and verify if the Export path still exist.

Expected Results

Without any intended changes made to the Export path, the setting should persist and at the end of the scan, the zip file should be exported to the saved path as expected

...
7/8/2021 10:43:24 AM : Start transport process.
7/8/2021 10:43:24 AM : Transferring file 85057_Single scan_2021-07-08_1007_0213.zip to export path C:\Users\Administrator\Downloads\Discovery import
7/8/2021 10:43:24 AM : File was successfully transferred.
7/8/2021 10:43:24 AM : Transferring file 85057_Single scan_2021-07-08_1043_0442.zip to export path C:\Users\Administrator\Downloads\Discovery import
7/8/2021 10:43:24 AM : File was successfully transferred.
7/8/2021 10:43:24 AM : Finished transport process.

Actual Results

The saved Export path disappears after a day or 2. This does not impact the Discovery scan itself but it affects the subsequent Discovery import to Insight, as there will be no file in the expected export path for the import

...
7/8/2021 10:07:33 AM : Start transport process.
7/8/2021 10:07:33 AM : No .zip files found.
7/8/2021 10:07:33 AM : Finished transport process.

Workaround

The scanned result can be found in the scans folder of the Discovery installation folder, as it will be first saved in the scans folder for packaging into a zip file and then exported. Possible workarounds are

• manually copy the zip file from the scans folder
• have a custom script in the server to copy the zip file from the scans folder to the targeted location automatically