Good Morning,
I continue to struggle to understand how the email trigger is functioning and why some (not all) of the tasks associated to the trigger fail. I have tried changing my approach and simplifying what is being done to try to isolate where my issue is, and I find it failing at the most basic level.
My revised configuration consists of a single task acting on a trigger. I am happy to provide the configuration if someone would like to review it. It is very simple as described below:
1. Email Trigger watches a specific email account and downloads the attachments of any (all) emails it receives.
2. The attachments are downloaded to a folder and arrive in a sub-directory named by the email ID \temp\1234\attachments\*
3. A 'Write file' task is then run using the following {TRIGGER(4d706949-d4fa-43ce-89b2-81bd77177eac|c72df5ea-c269-4b44-81c7-4dea1bd954f2|Mail.Result.Mail.MessageId)} simply writing the '1234' email ID to a file within the download \1234 folder.
4. END
The Good
Every email received by the account successfully downloads. The email ID directory is created, and the attachment saved.
If a single email is present when the trigger is invoked the 'Write File' task completes with no issue.
The Bad
If more than one email is queued on the server when the trigger is invoked. The email ID directory is created and the attachment saved for each and every email (good). 5 emails = 5 folders and 5 attachments. 10 emails = 10 folders and 10 attachments.
The issue is the 'Write File' task. The general behaviour will be that the first file is successfully written, the second is not written, and the subsequent ones will mostly be written.
A case example:
10 emails staged to the server.
Trigger is invoked.
10 folders created.
Write File completed for email 1,3,4,5,6,8,9,10
No Write File occurring for email 2 and 7
In trying to understand the Trigger functionality, I would assume that each email is a trigger and and event unto itself. In my scenario there are 10 emails, and the process is triggered 10 times. one for each email received. Am I correct in this assumption?
I see nothing in the logs indicating why this is failing, and can't get past this hurdle. The end game is that I need to retrieve content from the email itself but if I can't rely on the basic behaviour, the more complex has no hope of succeeding.
Dying to figure this out. I am now running the release 6.1.9 having hoped it may have resolved something.
Chris