Emailers Not Working on just 2 workbenches

Question

I have two workbenches, in which the emailers fail every night, the error being:

Emailer_<Rejected> (TeeFactory): Emailer_<Rejected>: Termination Message: 'Emailer output a <Rejected> feature. To continue translation when features are rejected, change 'Workspace Parameters' > Translation > 'Rejected Feature Handling' to 'Continue Translation''

Error encountered while calling method `input'

for the one that runs first, and:

Emailer: <class 'TimeoutError'>: [WinError 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

for the second. First is an all out error that terminates the workbench, the second just being a warning, but the outcome is the same - no emails sent!

It works perfectly fine on FME Form, and it was working perfectly fine on FME Flow for the last 2 months, now all of a sudden, it has stopped. This isn't affecting any other workbench, I have 20 more running on Flow that send emails perfectly fine. Both these jobs are scheduled to run nightly at 20:45pm.

I have tried removing the emailers from the workbench and adding them back in, and republishing, to no avail. I have also deleted the jobs off of Flow entirely and republished them but that doesn’t work either. I have checked the configuration of my emailers, and they are identical to every other workbench.

My next move is to move one schedule to slightly earlier, and see if its the clash that is causing the issue.

Versions as below - I can’t update either of these at the time being, due to the Windows version in my Organization. It is due to be updated soon though.

Form Version: FME(R) 2021.2.6.0 (20220727 - Build 21821 - WIN32

Flow version: FME Server 2022.2.5 Build 22795 - win64

Page 1 / 1

We too have nightly jobs running, and they often encounter strange problems including timeouts.

Often moving the schedules slightly can have a beneficial impact. Other servers may be preoccupied at certain times, and it’s more often than not impossible to predict when. So it’s really up to guessing when the right times are.

On top of that, our system prevents my local Form from mailing, whereas the same workspace works fine on our server Flows. Just adding to the difficulties. At least you seem to not have that problem.

Reply

lifalin2016 · Answer

We too have nightly jobs running, and they often encounter strange problems including timeouts.

Often moving the schedules slightly can have a beneficial impact. Other servers may be preoccupied at certain times, and it’s more often than not impossible to predict when. So it’s really up to guessing when the right times are.

On top of that, our system prevents my local Form from mailing, whereas the same workspace works fine on our server Flows. Just adding to the difficulties. At least you seem to not have that problem.

Reply

Community Stats

Sign up

An FME Account is required to contribute

Login to the community

An FME Account is required to contribute

Scanning file for viruses.

This file cannot be downloaded