You are viewing limited content. For full access, please sign in.

Question

Question

Workflow Emails - missing PDF/email attachments randomly

asked on November 19, 2019

Hi All

 

We have a workflow that emails client invoices, 1000s per day.

 

This is fairly simple, billing is scanned and added to LF via a QF job, workflow is then triggered, pull a profile for the email address from a DB and then creates a email and attaches a PDF of the invoice.  All very standard workflow stuff.

 

Problem.  In a give day a dozen or so emails are sent, but don't have the attachment.  There is no obvious pattern to the emails that are missing attachments.  Failure rate is low but with billing it is a daily problem.

 

If I track down and re-process a failed email, on the second time through the email sends correctly with the attachment.

 

So...  any suggestion on how to correct this issue/bug?   I need a way to confirm that the billing email has an attachment if it does not, then abort and retry or similar?

 

With thanks

 

Jeff

 

0 0

Replies

replied on November 20, 2019

Do you see any warnings in the instance that fails to send the attachment? If not, then as far as Workflow knows, the document was sent, so you'll have to look at the mail server for why it wasn't sent.

0 0
replied on November 20, 2019

I have pulled the logs, SMTP-IN log snippet screenshot - working and not working, meaning has attachments and does not have attachments - note the email size.

 

The email coming from Workflow is 1300 bytes, this is too small - it has no attachment.

 

A working email with attachment:

Wed 2019-11-20 08:57:14.055: Creating temp file (SMTP): d:\mdaemon\queues\temp\md50000182847.tmp
Wed 2019-11-20 08:57:14.055: --> 354 Enter mail, end with <CRLF>.<CRLF>
Wed 2019-11-20 08:57:14.297: Message size: 609651 bytes

 

Email that should have an attachment:

Wed 2019-11-20 08:57:15.465: Creating temp file (SMTP): d:\mdaemon\queues\temp\md50000182848.tmp
Wed 2019-11-20 08:57:15.465: --> 354 Enter mail, end with <CRLF>.<CRLF>
Wed 2019-11-20 08:57:15.465: Message size: 1300 bytes

lf_WorkingAttachments_2019-11-20.png
lf_missingAttachments_2019-11-20.png
0 0
replied on February 20, 2020

I've also experienced this issue and started digging into the event log. I'm able to correlate the below event with the instances when this occurs. Is Workflow attempting to run some external process to prepare the attachment?

Sadly there is not much info here but might point in the general direction.

 

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

  <Provider Name="Application Popup" Guid="{47BFA2B7-BD54-4FAC-B70B-29021084CA8F}" />

  <EventID>26</EventID>

  <Version>0</Version>

  <Level>4</Level>

  <Task>0</Task>

  <Opcode>0</Opcode>

  <Keywords>0x8000000000000000</Keywords>

  <TimeCreated SystemTime="2020-02-19T11:08:29.262575600Z" />

  <EventRecordID>589976</EventRecordID>

  <Correlation />

  <Execution ProcessID="552" ThreadID="10172" />

  <Channel>System</Channel>

  <Computer>sym-01-lfproc1.hra.local</Computer>

  <Security UserID="S-1-5-18" />

  </System>

- <EventData>

  <Data Name="Caption">Laserfiche.Workflow.Activities.83.Processor.exe - Application Error</Data>

  <Data Name="Message">The application was unable to start correctly (0xc0000142). Click OK to close the application.</Data>

  </EventData>

  </Event>

 

0 0
replied on February 20, 2020

Yes, exporting documents goes through Laserfiche.Workflow.Activities.83.Processor.exe. Anything in the application event log from Windows Error Reporting about it?

0 0
replied on February 20, 2020

Nothing in "Windows Logs -> Application".

This is the only thing I could find. It's in "Windows Logs -> System".

I searched through the error logs in the Admin Console and couldn't find anything there either.

While it seems to happen on a rare occasion with a single email. It usually happens in a clump when many emails get sent in quick succession. In the most recent case I had there were 31 successive emails that failed to have their attachment added.

This was over a two minute window. Emails immediately before and after went out fine.

They are separate workflow instances, which might indicate there could be concurrency issues at play.

 

 

0 0
replied on February 20, 2020

If you resend just the one that failed, does the document export fine?

0 0
replied on February 20, 2020

yep

0 0
replied on November 12, 2020 Show version history

Good day,

 

Was this issue resolved? Im experiencing the same issue.

 

Kind Regards,

Pearl

0 0
replied on November 12, 2020

Can't say it was resolved, but we were able to mitigate it at least. I noticed that the issue seemed to get worse over time. One day it might be a couple emails, then the next it would be dozens.

It seems there is some resource not being released, maybe a process handle, that eventually leads to the issue.

We set up an automated restart of the workflow service once per night, and that all but eliminated the issue for us. It still happens to a single email every now and then, but that is a far cry from the issue we had prior to it.

Hopefully that'll help you as well. Should have posted the "fix" here once we figured out how to get around it for now.

 

1 0
replied on November 13, 2020

Thank you so much.

0 0
replied on April 5, 2022

Bump on this, still an ongoing issue.

0 0
replied on October 30, 2024

Fairly certain this has something to do with the creation of the PDF for the attachment. I have a workflow issue I'm troubleshooting that's throwing the same errors in event viewer. There seems to be either a "hold" on a process that results in the export of 1kb empty documents. 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.