The easiest is probably to use a secondary workspace that executes the workspace using a WorkspaceRunner transformer. The “Failed” port of the WorkspaceRunner can then be used to trigger an Emailer transformer.

To add to David’s solution, if you create a user parameter linked to Workspace Parameter/Logging/Log File in the original workspace, you can create a feature attribute that stores a log file path in the second workspace, pass it to the Log File parameter of the original workspace through the WorkspaceRunner, and then attach the log file to the email if the translation failed.

Thanks! I will have a look. And in FME server, could I filter the logs to get only the ones related to this workspace? A trigger that would send an email if an error occurs within that workspace?

yes you could! you would need to configure an automation to run the workspace  and connect the failed port to email action.

just be sure to configure the email body of the email action to refer error msg / error type parameter using the text editor

Try this workspace which will pull the entire log file for you, store it in a postgres db, and send the snippet with the full error, not just the “See log file above for more details” error that it usually sends you using your method above.

I did set it up on FME flow to be triggered whenever an error does occur.