Hi Richard, thanks for taking the time to work on this. We have tried attaching shortcuts OR copies of the document. We've tried PDF or just the electronic document. It doesn't seem to matter what workflow or what type of attachment we select, from this new workflow server we can't seem to get any type of attachment to work. The strangest thing of all to me is the fact that there are no workflow errors. We've also looked through the windows event log both in Applications and Systems as well as the Laserfiche specific LFS and Workflow event logs and it appears very clean.

An issue I was having was the document was changing from the time of the "find" activity, till the email activity. That change seemed to break the link and the document would not attach. 

What I did was to put a delay just before the email activity, then after the delay it would find the document, then attach it to the email immediately afterwards. That delay would give the server time to update metadata if it needed to.

Have you tried to set up a simple Business Process to test? One with just a find activity and then an email activity? This way you can control when to initiate the email and also keep it very simple and eliminate anything upstream that may be holding you back.

I still don't think it's a Workflow issue. You can check the Activities tab in the instance details and look at all completed activities. There should be separate rows for X_Entry_0*, X_EmailWithAttachments*, X_DeleteWFFile*, where X is the name of the Email activity. Those are the inner activities that export the file when you have as attachment. If any of those failed, you'd have seen errors in the instance. If the document had no content to export, then WF would've written that as a warning in the message itself.

Any anti-virus on the machine?

Miruna, normally I would completely agree with you. That's what seems so strange.

Nope, no AV active on the machine. Yes, I see those sub activities you describe and there are no errors. Until I setup that SMTP server right on the workflow machine and delivered email from workflow to that SMTP server and read it with a generic pop3 client where the email was delivered to 127.0.0.1 and read from the same I would not have believed there was anything wrong with workflow. I'm still scratching my head.

The only good news is that it's for our own internal workflow server in our own company with our Avante license so it's not like a customer is down but we still need to figure this out somehow.