I am noticing that even if I set my workspace in Workbench to terminate on rejected features, it runs without error on FME Server. Is the rejected feature handling a workbench-only feature? I am expecting to see the same behavior on FME Server. I'm using 2017.1 in my testing. Thanks.
Solved
Rejected Feature Handling on FME Server
+6Best answer by brianatsafe
Happy to announce that this issue has been fixed and will be available in FME 2018.1.
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+20- Safer
- 3719 replies
Hi @dbaldacchino,
It should be the same as whats set in the workspace. Can I ask which transformer(s) you are seeing the wrong behaviour in?
+6Hi @MattAtSafe,
I'm using an HTTPcaller. The workspace terminates in workbench but not on FME Server (I have to add a terminator to get the expected behavior on FME Server).
+20- Safer
- 3719 replies
Hi @MattAtSafe,
I'm using an HTTPcaller. The workspace terminates in workbench but not on FME Server (I have to add a terminator to get the expected behavior on FME Server).
Thanks I've taken a look into the system and it seem like this is a know issue for the HTTPCaller (and some JSON transformers). I have linked this Question to the internal prblem report. Thanks for sharing your worksaounrd and I'm sorry for the inconvenience this bug may have caused.
+6Hi @dbaldacchino,
Thanks I've taken a look into the system and it seem like this is a know issue for the HTTPCaller (and some JSON transformers). I have linked this Question to the internal prblem report. Thanks for sharing your worksaounrd and I'm sorry for the inconvenience this bug may have caused.
+13- Safer
- 92 replies
- Best Answer
Happy to announce that this issue has been fixed and will be available in FME 2018.1.