Skip to main content
  • EN

I'm working on FME Flow and trying to build in a way to identify and catch database errors that occur in my workspaces that run on FME Flow.


If my FeatureWriter (or Writer) fails to write to my database I would like to identify the error(s), such as the user has no rights to write to the database or the database is not available, and send them as an email. Since there is no <rejected> port on the FeatureWriter, is there any other way to catch these kind of errors than to access the log file of the failed job via an HTTPCaller and the REST API and to see if the ERROR/WARNING messages contain keywords such as "MSSQL Writer" that identify the errors as database errors? 

 

/Vera

You could try using the LogMessageStreamer to look for warnings and errors during the translation, rather than parsing the log file after the fact.

Also, please help improving the FeatureWriter by upvoting this idea :-)

 

Thanks for the suggestion! I was looking at the LogMessageStreamer but I felt like it does not really solve my problem… If the FeatureWriter fails it just terminates the workspace and I can’t access the data the LogMessageStreamer has caught 🤔 but I’ll maybe look a bit more into it, maybe there’s another way!

 

Yes I found that idea, already voted for it 😁

Community Stats

31,927
Posts
121,266
Replies
39,553
Members

Latest FME

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.