+29Create a Trigger in Automations for failed job (that would be applied globally, so whenever a job failed either manually ran, scheduled, or through an automation or subscription, it would trigger the automation.
This would allow users to use actions such as filtering before sending an email.
+29Would like to see the following attributes included (but not limited to) that could be parsed out: Job ID, Repository, Workspace, & Error Messages from log
+29Can remove this as it's already possible :)
Open up the fmeServerConfig.txt file and look for #NOTIFY_JOB_FAILURE=<TopicName> and uncomment the line and set the <TopicName> to a topic you setup in FME Server. Then have that topic post to a subscription that triggers a workspace that sends the email. I had the last part setup on my FME instance, but manually added the failed job topic to all the schedules and automations instead of using this *doh*... Additionally you could use automations after the topic gets notified and do filtering that way (Which I think would be a lot easier)
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
