Is there any way to display the job id when a workspace fails when it is executed through a FME Server app ? Currently when a FME server app fails, it just displays a Failure message. I know I can probably do an automation and send an email with that info somehow, but it would nice to just have the job id displayed with the Failure message.
+2- Contributor
- 606 replies
Hi @mferwerda1111 ,
This is a great question. I spoke with the team regarding this and found out the failure message is purposefully kept with minimal information but the job id could be included in that message. The best way to help this make it's way into FME Server would be to post a new suggestion on the Ideas page so other users can upvote and comment with their wish list/use cases for this as well!
+2- Contributor
- 3 replies
Is there any way to display the job id when a workspace fails when it is executed through a FME Server app ? Currently when a FME server app fails, it just displays a Failure message. I know I can probably do an automation and send an email with that info somehow, but it would nice to just have the job id displayed with the Failure message.
Yes, I absolutely agree. I am writing an App that uses a workspace that has error handling message feedback. I need the App to display the messages that appear in the Log files. My work around is to post this general message:
- Source DWG File : Drag and Drop your Import.DWG file into the Browse Resources DWG File \ Upload File box
- DWG Feature Types to Read : Defaulted ON. If you do not want to load in certain feature types, then deselect them accordingly
- Alternative/Design : Set value according to the PLAN alternative you are working in. For example "|DM Top|PLAN_6875309" Replace "|DM Top|PLAN_XXXXXXX" with the correct string
- Make sure you close the project you are importing the data into as FME Server can only load data into GIS if the Alternative is not in writable mode
If the translation fails, the source data features may be:
- Outside BC's Service Area
- You may have a floating feature in your ACAD file
- The entire dataset is in the wrong location
Check your Import.DWG, verify the units, projection (Source) and coordinates. Units must be in meters. Source projection must be in BC Albers meters not millimeters