Re-process files on failure
Post any question you may have in regards to GoAnywhere MFT and let our talented support staff and other users assist you.
If you need a quicker response, please create a support ticket via the customer portal my.goanywhere.com or contact our support team by email at [email protected].
If you need a quicker response, please create a support ticket via the customer portal my.goanywhere.com or contact our support team by email at [email protected].
3 posts
Page 1 of 1
- Posts: 4
- Joined: Fri Aug 05, 2016 5:32 pm
- Location: Birmingham, AL
Hi,
I have several processes that monitor a directory for a given file (or files), perform some manipulation on them (rename, upload, etc) and then archive the files. These are kicked off from a filesystem monitor directly on the MFT server. One of the last steps (after the uploads, etc) is to remove the source file so it's not processed again the next time the monitor runs. However, we've run into situations where, if the process fails for whatever reason (usually a transient communications issue with the remote site) we *want* the monitor to pick up on the same file and attempt to process it again. However, because the monitor has already "seen" the file, it just ignores it.
What's the best way to work around this? I thought about having an "error" module that updated the timestamp on the file (kind of like the unix "touch" command) so it would look like a new one, but wanted to make sure there's not a better way to go about this.
I have several processes that monitor a directory for a given file (or files), perform some manipulation on them (rename, upload, etc) and then archive the files. These are kicked off from a filesystem monitor directly on the MFT server. One of the last steps (after the uploads, etc) is to remove the source file so it's not processed again the next time the monitor runs. However, we've run into situations where, if the process fails for whatever reason (usually a transient communications issue with the remote site) we *want* the monitor to pick up on the same file and attempt to process it again. However, because the monitor has already "seen" the file, it just ignores it.
What's the best way to work around this? I thought about having an "error" module that updated the timestamp on the file (kind of like the unix "touch" command) so it would look like a new one, but wanted to make sure there's not a better way to go about this.
- Support Specialist
- Posts: 590
- Joined: Tue Jul 17, 2012 2:12 pm
- Location: Phoenix, AZ
-
Upgrade to version 5.4.3 ... this will give you an option to see if "FILE EXIST" instead of Created or Modified.
This is the reason this was added to the product.
This is the reason this was added to the product.
Rick Elliott
Lead Solutions Consultant
(402) 944.4242
(800) 949-4696
Lead Solutions Consultant
(402) 944.4242
(800) 949-4696
- Posts: 4
- Joined: Fri Aug 05, 2016 5:32 pm
- Location: Birmingham, AL
Very nice! I'll schedule the upgrade for this weekend. Thanks...
3 posts
Page 1 of 1