SMTP Error with Workflow

asked on January 11, 2019

Hi all,

I'm having a problem with an external SMTP server and workflow.

On my Windows server, I'm running LF Workflow 10.2 and osTicket (PHP app in IIS). I've tried the same configuration (SSL on port 465) with both apps. The mail connection works with osTicket but not with WF, so I suspect credentials and firewall isn't the issue. Is there something else I can look at?

This request operation sent to net.tcp://localhost:8085/ManagementService did not receive a reply within the configured timeout (00:00:30). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.

-Ben

0 0

replied on January 13, 2019

Hey Ben,

Have you tried this...

https://support.laserfiche.com/kb/1012896/modifying-connection-and-operation-timeout-limits-for-workflow-8-3

Help me with a SMTP timeout on a Workflow.

Jono

1 0

View 1 previous reply

replied on April 15, 2021

Hi Jonathan, with this registry configuration you finally solved the issue¿?... I have been trying with high values but the issue still happen but only some days.

0 0

replied on April 15, 2021

Hi Robinson-

I had this issue happen intermittently last year. It seemed related to spam filtering, that Workflow was sending too many emails in short succession. My coworkers that handle that side of things were unable to get any working exceptions, so I took care of it within the workflow itself.

Here's the gist:

This logic goes in a repeat loop so it can try again
Email gets put in a try-catch block
Catch block delays for 2 minutes if there is an error
After 2 minutes, try again
Once successful, set a token to flag as "successful" in order to break out of the loop
To make sure it doesn't keep going indefinitely, I limit the repeat to 100 iterations (I think it's only ever done 2 or 3)
Within the Catch block, if more than 95 iterations have occurred, rethrow the error so that I know the problem happened again. Luckily, this has never happened. NOTE: I ran into some issues trying to get that iteration check to match the iteration limit, hence setting it 5 lower.

2 0

replied on April 16, 2021

Hi Pieter, for our case we finally found that sending notifications using an office 365 account only allows until 30 messages per minute so we had to limit to that number using a workflow. And also we are using a similar aproach to your sample workflow to control the errors. Thanks for your reply.

1 0

Question

Question

Replies

Sign in to reply to this post.