"Proceed to the next application regardless" not working sometimes for NetSuite import (SuiteApp SuiteScript 1.0)?

[geofftipley]

Greetings, I configured an import component with the "Proceed to the next application regardless" setting that allows a record to pass to subsequent components even if there is an error. The client wants the errors mapped to a certain field in a second import component's mappings and my solution is usually reliable.

But on Monday the client reported to me that a record was stuck on the first import step and provided a screenshot showing the error in "Open errors":

My expectation is that when I've set an import to NOT use the default of "Pause here until someone can fix the error.", that all records should always pass through this component, whether the import had an error or not.

This import component is NetSuite, using the NetSuite API version of "SuiteApp SuiteScript 1.0" and I'm wondering if certain classes of NetSuite error are unable to pass through to following components using the "Proceed to the next application regardless" when an error is encountered.

[tylerlamparter]

Having the "Proceed to the next application regardless" option still throws an error for the step it occurred on, and it also passes the record through to the next step. If you want the error not to show up at all on the import step where these failures occur, you would need a postSubmit script to mark it as ignored. You can find the docs on how to do this here: https://docs.celigo.com/hc/en-us/articles/360045807112-Ignore-specific-errors-in-a-postSubmit-hook.