No upload email being sent

Question

I'm trying to send an email when files get uploaded but they don't generate. If I flag download and delete as well, then these emails are generated at the appropriate times but the upload email never happens.

Even if I overwrite an existing file with the upload - i get the delete email for the file but no upload email.

Any ideas why please?

Answer 1

I think we'll need to see a log file to be able to troubleshoot this problem.  Can you please open a ticket at enterprisedt.com/help and attach a debug-level log file?

Comments

...............................

---

Hi
Just a quick thought - does it constitute an "Upload" if I am using a client like WinSCP and logging in as a user and then dragging a file from my local PC to the SFTP site? It triggers the "Delete" if it has to overwrite the file but no "Upload" is triggered. Yet, when my client uploads a file from their site - the "Upload" is triggered and I receive the email.
Thanks
RIck

---

"Just a quick thought - does it constitute an "Upload" if I am using a client like WinSCP and logging in as a user and then dragging a file from my local PC to the SFTP site?"

Yes it does

"It triggers the "Delete" if it has to overwrite the file but no "Upload" is triggered."

Are you saying that if you try to upload a file over the top of an existing file then the Delete event is triggered, but the Upload event is not?

---

Hi
Yes, in testing where I keep dropping the same file over and over again via WinSCP, I get the delete email triggered but no upload email. If it is a new file that does need to be overwritten, I get nothing at all. And indeed, if I add a download trigger and drag the file from the SFTP back to my local drive, I get the download email triggered. So, it seems its just the upload that never triggers.
But to complicate that, if my client/customer uploads their daily file to me via the SFTP - I do get the upload email triggered. That's why I was wondering if it was something to do with me being 'local' that was causing the issue.

---

I've asked a tester to investigate this.  We'll get back to you soon.

---

Our tester has been unable to replicate this behaviour with the current version (10.1.1).  Which version of CompleteFTP are you on?

---

Hi
Version 9.1.1

---

OK, it's probably worth updating to the latest version as there were some fairly major changes made to the way that events are fired recently.  If it still doesn't work then I think we're going to have to look at your logs.

---

Hi
Was a bit puzzled why it works when my client uploads a file so tested some more.
Its odd but it seems to be if I transfer a .csv file I don't trigger the upload.

I tried testing in my clients live directory - the Folder Filter is set to /GUHealth/FromAU/GUHEALTH*.txt and when I move a .txt file there, it triggers the email not a problem.

I changed the Folder Filter to /GUHealth/FromAU/GUHEALTH*.csv and renamed the local file to .csv and tried to move that across - no email triggered.

Reset the Folder Filter back to .txt, renamed the local file back to .txt, moved it over and email gets triggered again.

Is there something odd about .csv files?

---

Not that I know of.

---

I changed the Folder Filter to be /GUHealth/FromAU/GUHEALTH*.* and I now get the email when I transfer both the .txt and the .csv files.
Difference is - in the email I show %FILENAME% and on the .csv email it shows GUHEALTH__test.csv.filepart rather than just GUHEALTH__test.csv

---

Great.  That explains it then.  The upload doesn't match the filter until the client renames it after it's finished uploading it.  So you'll need to select the rename event as well.  That's very useful to know.  Does that explain all the behaviour you've seen?

---

So, the Upload trigger runs whilst the upload is still in progress and the file hasn't been renamed yet like it does on successful completion? But only on CSV's?

I don't seem to have a Rename event in the Events section.

---

The event you want is called 'Move file' rather than rename.

I can't think why it should have anything to do with the extension of the file, though our tester has just reported that she's seeing different behaviour depending on the size.  Could that be the problem?

Regarding the upload event.  The upload event would've triggered when the upload was completed, but at that point the name of the file was XYZ.filepart and therefore didn't match your file filter.  I guess you could change your file filter to also match .filepart; that way you won't have to worry about the move event.  You can do this using a regular expression as follows:

regex:/GUHealth/FromAU/GUHEALTH*\.csv(\.filepart)?

The brackets around the last extension followed by the question-mark indicate that it's optional.

---

The files size I have been testing with is only 134KB so not large at all.
Also, %TransferStatus% shows 'successful' on the Upload triggered email.

Move event works - and shows %Filename% without the .filepart.

Problem is, for a .txt file you only get the Upload trigger and no Move trigger but for .csv you get both.

May have to use the regex option instead.

Wonder why the difference in operation for .csv versus .txt