IMAP4 Reader <MessageID>

Thanks Mike. Sorry for being a problem. No stress as I have reworked this specific package. But the solution is floored in the sense that I can't use the same pattern for other collections.

<MessageID> is perfect for our requirements and as mentioned works in all other cases except where we seem to get the messages that match this criteria all at the same time. Perhaps there is something in the message header related to UID that is throwing a spanner in the works. This rare but did crop up in our testing.

I can make {GUID} work as well except that in my case at least when I have replaceable variables in the same File Input field as the GUID, the GUID retains the curly braces which means that if this final name and path are stored in a variable - the curly braces are recalculated again resulting in an error.

I did try to use a dynamic name based on system date and time but the time difference (fractions of seconds) is not small enough and they are treated as the same set again.

cheers

Hi Bruce

You can also try GUIDNB Transformation language function, it returns a clean GUID value without brackets and underscores
You can also use <Current Package Action GUID> variable.
GUIDNB is recalculated every time it is used

<Current Package Action GUID> is populated before the package action exection