Skip to main content
Question

FME Form and FME Flow - Emailer Question

  • April 21, 2026
  • 3 replies
  • 54 views
teachcalds
Contributor
Forum|alt.badge.img+4

Hello Everyone,

 

I have an FME Flow 2025.2.4 automation that contains nineteen individual FME Form 2025.2.4  jobs. In addition to those nineteen jobs, I have two separate FME Form jobs that are used only for email notifications. One notification job is intended to run when jobs succeed, and the other is intended to run when jobs fail. Both of these notification jobs contain an FME Form 2025.2.4 Emailer transformer in their build.

 

All nineteen FME jobs in my automation are connected to the Success notification job through their success ports, and those same nineteen FME jobs are connected to the Failure notification job through their failure ports. This wiring ensures that the appropriate notification workflow is triggered depending on the outcome of each job.

 

The goal is not to send an email for every individual job result. Instead, the goal is to send a single consolidated email per outcome type of Succeed and/or Failure. For example, if nine jobs succeed and ten jobs fail during an automation run, the desired result is two emails total:

 

  • One email listing the names of the nine successful jobs
  • One email listing the names of the ten failed jobs

 

If all nineteen jobs succeed, only one success email should be sent containing all nineteen job names. Similarly, if all nineteen jobs fail, only one failure email should be sent containing all nineteen job names.

 

  • One email listing the names of the nineteen successful jobs

 

Or

 

  • One email listing the names of the nineteen failed jobs

 

To achieve this, each of the nineteen jobs needs to pass its own job name to the notification jobs at runtime using automation output attributes. The success and failure notification jobs then collect all incoming job names, aggregate them within the workspace, and generate a single email per outcome with a complete list of job names.


I am trying my hardest to avoid excessive daily email notifications while still providing clear visibility into which jobs succeeded or failed during each daily automation run.
 

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 

 

Example of Success Email:

 

The following FME jobs completed successfully:

 

  • {job.workspace} (JOB 1)
  • {job.workspace} (JOB 2)
  •     ↓           ↓            ↓
  •     ↓           ↓            ↓
  •     ↓           ↓            ↓
  • {job.workspace} (JOB 18)
  • {job.workspace} (JOB 19)

 

Next steps:

• Review the job logs in FME Flow to confirm successful completion

• Verify expected outputs or downstream data updates

• Ensure no warnings or unexpected messages were generated

 

Thank you,

FME Flow Admin

(This message has been generated by the FME Flow Team)

 

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 

 

This all sounds great and it seems doable, but all attempts I have made expose my lack of expertise in notifications like this. Does anyone out there know the steps I would need to take to make this a reality in FME Form 2025.2.4 and FME Flow 2025.2.4?

 

Thank you in advance for your time and expertise! It is always so appreciated!

    3 replies

    crutledge
    Influencer
    Forum|alt.badge.img+46
    • crutledgeInfluencer
    • Influencer
    • April 21, 2026

    Hi ​@teachcalds I am not the expert here but looking to do something like this. I was going to approach this from another direction. If we look at designing this in 2 parts. 

    Part 1 - Do the work, run series of scheduled automations. Some are successful some are not.
    Part 2 - Read the log files and summarize success and fails, then generate message and email.

    If we look at the out of the box examples for Dashboard reporting one of them is Success/Fails. I was going to modify this for my needs. 

    I am not there yet but I hope that helps!

    At your rest service ^B
    matthias_ct
    Contributor
    Forum|alt.badge.img+4
    • matthias_ctContributor
    • Contributor
    • April 22, 2026

    One possible approach is to use a Split-Merge Block in combination with the FME Flow REST API:

    • Configure the Split-Merge Block as shown in the screenshot.
      Do not connect any output port to the Split-Merge Block’s output port. This ensures that exactly one feature is emitted once all jobs within the block have completed, see https://support.safe.com/hc/en-us/articles/25407747491597-Understanding-the-Split-Merge-Block-Troubleshooting-FAQs
    • As a result, the downstream workspace (which is responsible for sending one or two emails) is executed only once.
    • This workspace should include a parameter that contains the event_id, which is passed from the trigger.
    • Within the workspace, use the REST API to retrieve all relevant jobs:
      • First, call:
        fmeapiv4/jobs?status=success&status=failure&sourceType=automations&sourceID=<automation_id>
      • Then, you get an array. Each element of this array contains the job_id. For each job_id call:
        fmeapiv4/jobs/id
    • Each job payload includes an event_id. By comparing this value with the event_id provided via the workspace parameter, you can identify which jobs belong to the triggered automation.
    • Once the relevant jobs are identified, use their job status to control the logic. Based on this, create one or two features and pass them to the Emailer transformer.
      teachcalds
      Contributor
      Forum|alt.badge.img+4
      • teachcaldsContributor
      • Author
      • Contributor
      • April 23, 2026

      Decided to remove this reply

      Community Stats

      32,503
      Posts
      123,449
      Replies
      40,702
      Members
      Terms & ConditionsCookie settingsAccessibility statement
      A product of
      Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.