Orderful Import is ignoring records with no input filter

Integrator.io
, ,
1

I have the following flow. There's no filters on the Orderful Import at the end.

The image depicts a workflow diagram consisting of three labeled blocks: "Get Load 240806" (Export) and "GetLoadEvents240806" (Lookup) linked to "Import Load Events" (Import), with interconnected elements and additional functional icons. (Captioned by AI)
The image depicts a workflow diagram consisting of three labeled blocks: "Get Load 240806" (Export) and "GetLoadEvents240806" (Lookup) linked to "Import Load Events" (Import), with interconnected elements and additional functional icons. (Captioned by AI)1390×221 16.2 KB

And yet it's ignoring the last step.

The image shows a run console interface with three completed steps, displaying details such as status, success, errors, and duration. (Captioned by AI)
The image shows a run console interface with three completed steps, displaying details such as status, success, errors, and duration. (Captioned by AI)1088×279 33.1 KB

Any clues on why that is?

2

Hi @jackharris - there must be a setting in the Orderful import step that is causing it to get ignored. In some imports for example, if the record already exists in the system then it gets ignored. I'm wondering if something like that is going on.

1 Like
3

It could also be an issue with your script on the orderful step. If it's outputting an empty record, then IO ignores it. I'm not sure what type of script is there based on the screenshot.

1 Like
4

I was able to find that the pre-map script on the Orderful step was creating a blank record when run. No clue why. The purpose of the pre-map was to get Interchange, Group, and Transaction Set Control Numbers. So, I split the script up into the earlier steps of the process. It creates the Interchange and Group in the initial export call and then makes the Transaction Set Control Numbers on the second lookup because I need one per response.

2 Likes
5

I had someone new working with Celigo today. He encountered an error where a step was ignored due to an empty script result. However, it’s not very clear in the UI that this is the reason. A UI update to show the cause of the ignore more clearly could be helpful. Not very important, but helpful :slight_smile:

1 Like
6

With the upcoming logging feature, you’d be able to drill down into the run history for a given run and see what happened to each record.

2 Likes
7

When does that come out?

8

Without getting myself into too much trouble, our current goal is H1 2026.