We have an ION Data Flow that processes new employees coming from Infor HR Talent.
Before sending the Process.Person BOD to Infor LN, the flow performs an API lookup to check whether the person/employee already exists in LN. This lookup is executed through an ION API Trigger step that calls the LN Employee API.
When the person does not exist in LN, the LN API returns:
Response code: 404
Response message: Not Found
{
"error": {
"code": "ERROR:ttstps0192",
"message": "Record ['XXXXXXX'] cannot be read from table Employees - General in company : YYYY."
}
}
Because of that, the API Trigger step generates an error object instead of producing the normal output document. Once the step enters this error state, the Data Flow cannot map the LN response into our custom JSON output document, and the flow stops.
However, what we actually need is the opposite:
We want ION to pass through the 404 response as a normal JSON payload, so we can map both:
- a successful LN API response, and
- an error response (404)
into our custom output JSON document.
This allows the Data Flow to continue and apply business logic based on either outcome.
1. How can we capture the 404 “Not Found” response as a normal JSON output?
ION currently treats the 404 response as a technical failure, which prevents the API Trigger step from producing the expected output document. We need a way for ION to treat “person not found” as a valid business condition, so the Data Flow can continue and map the LN response—whether success or error—into our custom JSON output structure.
2. Why does the LN API return an error when the record does not exist?
From the LN API perspective, returning a 404 Not Found is correct behavior for a missing record. But in an ION Data Flow, this causes the API Trigger step to fail instead of returning a usable JSON response. This prevents us from handling the lookup result and stops the flow prematurely.
We are looking for guidance on how to configure ION so that a 404 response can be handled, mapped, and used, rather than treated as a fatal error.
I hope i am not the first person in this situation , all the support and tips are appreciated.
Regards
Mulugeta
