Skip to main content

I'm attempting to use the following email template with FME Server 2015.1.3.2 :

<fmeblock>

This notification e-mail was generated automatically from FME Server (PROD). Please contact your system administrator or submit a service ticket for support. Do not reply to this e-mail.

FME transformation job {id} has FAILED.

Workspace: {workspace}
Repository: {repository}
Status: {StatusMessage}
Submitted: {timeRequested}
Job Start: {timeStarted}
Job End: {timeFinished}
Logfile: {logFullPath}

</fmeblock>

{workspace} & {repository} are both returning "_undefined_". All the other macros seem to work fine. Any suggestions?

I suggest to monitor the topic notified and see if the workspace and repository values are in the json notification data.


It seems these keywords were not available until FME Server 2016.

See this article: missing keywords


It seems these keywords were not available until FME Server 2016.

See this article: missing keywords

I agree.

 

This is what I can see on a 2015.1.2 Server:

 

{
    "ws_topic": "CCD_NOTIFICATION",
    "id": "25436",
    "StatusMessage": "Terminator: Aborting Translation as directed by mapping file. Message is 'Unexpected error!'.",
    "LogFileName": "job_25436.log",
    "timeFinished": "Fri-13-Jan-2017 02:27:35 PM",
    "logHome": "C:/ProgramData/Safe Software/FME Server///Logs",
    "timeRequested": "Fri-13-Jan-2017 02:27:30 PM",
    "StatusNumber": "859017",
    "requestKeyword": "JOB_SUBMITTER_SERVICE",
    "jobsuccess_topic": "CCD_NOTIFICATION",
    "jobfailure_topic": "CCD_NOTIFICATION",
    "timeStarted": "Fri-13-Jan-2017 02:27:30 PM"
}

 


Same Problem on FMESerer 2019.1.2

 


Same Problem on FMESerer 2019.1.2

 

Hi @virtual,

 

 

Sorry that you are running into this issue, since you are in 2019 can you confirm if you are using Automations or still the old method Email Subscriptions?

Reply