Skip to main content

Hello all,

 

I have had an automation running for the better part of a year and I set it up to send me emails (post topic on failure). I needed to revise this and set up 2 separate automations to separate the types of jobs, daily vs every 30 minutes. Prior to setting up the new automations, I stopped the original and deleted it. It is still sending me emails now. I also made sure I replaced every instance where it was tied to a schedule, and I deleted the topic itself, and I am still getting emails. It has been stopped and deleted for over a month now and I am searching for a solution to end the emails. Any help or suggestion would be appreciated. Example below, it is sending failure notifications from over a month ago:

{"automation.id":"cac0de02-77e3-4c13-b330-dba1175dfaf7","workspace":"CMPT CG Future Allocation VW.fmw","timeRequested":"Wed-31-May-2023 05:00:00 PM","requestKeyword":"SERVER_SCHEDULER","timeStarted":"Fri-07-Jul-2023 11:40:52 AM","source":"topic","repository":"Comptroller-Finet Data","LogFileName":"job_29938.log","jobfailure_topic":"FME Comptroller Tables To GCP","StatusMessage":"SQLCreator_<Rejected>: Termination Message: 'SQLCreator output a <Rejected> feature. To continue translation when features are rejected, change 'Workspace Parameters' > Translation > 'Rejected Feature Handling' to 'Continue Translation''","StatusNumber":"798006","logHome":"C:/ProgramData/Safe Software/FME Server/resources/logs","timeFinished":"Fri-07-Jul-2023 11:40:53 AM","id":"29938","time":"2023-07-07T11:40:53Z","logUrl":"http://server information here/fmerest/v3/transformations/jobs/id/29938/log","event.id":"c5f15289-8595-4837-bef8-c33ea0de8608","automation.name":"Mike's FME Workspaces"}

 

Funnily enough, I encountered a problem with automations today which led me to this page, where someone has what looked like a similar issue (in comments)

 

https://community.safe.com/s/question/0D54Q00008iv212SAA/once-i-stoped-an-automation-and-again-i-want-to-start-is-its-giving-error-unable-to-enable-xxxxxx-there-was-an-issue-with-component-workspace-subscription-e39f275fb7d6400689a9bec0b5e5d8d7b9c6a63abc2d2914990635915d3c392d-already-exists


Thank you for your post @mikebrooks​ !

 

Could you please file a support case so that one of our specialists can dive into this with you? When submitting the case, please be sure to include the build of FME you are using, as well as any other relevant details to your set up (e.g. deployment type, etc.)


Reply