Skip to main content
  • EN

Hey, 

 

I have a question about the HTTP Caller. Is there a way to have the workspace it is in still continue even if one of the records fails to upload? The reason I ask is because there are some interesting errors I have ran into when uploading records to Cityworks, where something fails and then I have to re-run the entire workspace, after first deleting all of the inspections/work orders that were created. 

 

The error involves an encoded string not being compatible with FME. I would just like a way to run the entire workspace for all features and not have it cancel out on a failure. Any tips?

Is it failing by outputting a feature out the <rejected> port? If so, ‘capturing’ that feature with a logger (or other another error capture workflow) will stop the workspace from stopping.

 

Rejected Features may be one of the reasons a workspace stops running. Reviewing the rejected features before proceeding may give you a clue as to what the issue is.

If you would like to skip over the rejected features, you can either add a Logger to the <Rejected> output port or change Workspace: Rejected Feature Handling to Continue by right-clicking on the <Rejected> port and selecting the Continue option. 

Read up about Rejected Feature Handling modes. 

Community Stats

31,951
Posts
121,336
Replies
39,561
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.