".~#~_del_" temp folder names causing a headache
Posted: Tue Nov 14, 2023 5:53 pm
We have a flow that moves a lot of folders from a network location, onto the machine running switch, and then onto an archive location again on the network.
For some reason, we are finding that it's leaving behind folders that have been renamed and start with ".~#~_del_"
It seems to be the inject job that we use to get the folder is doing this. I believe it gives the folder a temp name prior to injecting it, and then renames it back to it's original name when done. But for some reason, there are always a number of folders left behind, as if it's not completed the operation.
Has anyone seen a problem like this before and if so, how do we overcome it?
The purpose of the flow is that we receive daily XML from an MIS with information regarding jobs that can be archived. So, we use this XML to go and retrieve the job folder and it's contents from the network storage and then move it to a specified archive location on the network storage.
Thanks,
Matt
For some reason, we are finding that it's leaving behind folders that have been renamed and start with ".~#~_del_"
It seems to be the inject job that we use to get the folder is doing this. I believe it gives the folder a temp name prior to injecting it, and then renames it back to it's original name when done. But for some reason, there are always a number of folders left behind, as if it's not completed the operation.
Has anyone seen a problem like this before and if so, how do we overcome it?
The purpose of the flow is that we receive daily XML from an MIS with information regarding jobs that can be archived. So, we use this XML to go and retrieve the job folder and it's contents from the network storage and then move it to a specified archive location on the network storage.
Thanks,
Matt