Skip to main content
Open

FME Server apps to return Errors

Related products:FME Flow
  • September 4, 2020
  • 9 replies
  • 226 views

virtualcitymatt
Celebrity

When using a FME Server App which fails for some reason there is no built in way to return an error message to the user. It is always an unknown problem.


It would be great if there was a way to return a few more details to the user. This is particularly important when an invalid dataset is uploaded.


Without a workaround there is currently no way to let the user know their data needs to be fixed.

9 replies

warrendev
Enthusiast
Forum|alt.badge.img+23
  • Enthusiast
  • September 4, 2020

This would be really helpful!


Forum|alt.badge.img
  • September 24, 2020

great idea !


anderstgd
Contributor
Forum|alt.badge.img+6
  • Contributor
  • March 19, 2021

Thank you for adding this idea! This is exactly what I was going to suggest.


reedwhit
Contributor
Forum|alt.badge.img+7
  • Contributor
  • April 16, 2021

could you email the log or message the user? when they run a long job.... or have an option to stream the Fatal parts of the log to the browser after the app runs.


thijsknapen
Contributor
Forum|alt.badge.img+10
  • Contributor
  • July 15, 2021

Hi @virtualcitymatt,

 

I struggled with the same thing. My preferred method would be to use a terminator message with a custom termination message for this. However, in the past it seemed that this termination message would only sometimes be returned to the user, and sometimes the message 'unknown error' would return.

Initially to work around the problem I would write the issues into an 'logged_items' excel and would return this to the user (using the data download service).

 

However it seems that the terminator issue is resolved in FME 2021.1, so maybe that could also help you out.


mgg_beca
Contributor
Forum|alt.badge.img+11
  • Contributor
  • November 14, 2023

I would love the ability to expose logger transformers to the app user while the app is running so you can log the results of specific processes. that way the user can see progress is being made. you could easily create custom error messages and log these as well. would be so much better than just thisScreenshot 2023-11-14 204025and then maybe something happens or doesn't.


Forum|alt.badge.img+1
  • January 22, 2024

Giving the specifics of a failure, or the output of loggers/terminators would be invaluable to users of flow apps. As opposed to a simple 'failed' message.

 

Often users are making simple errors with data inputs and parameters that is causing a lot of unnecessary back and forth. The majority of these issues could be self diagnosed with the ability to view these notifications. This is a significant issue for uptake of our developed apps.


LizAtSafe
Safer
Forum|alt.badge.img+15
  • Safer
  • February 10, 2024
The following idea has been merged into this idea:

All the votes have been transferred into this idea.

ecx
Supporter
Forum|alt.badge.img+4
  • Supporter
  • March 31, 2025

This functionality would be extremely useful

for anyone looking for the workaround:
 

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings