uncaughtException in Bulk Create/Update/Delete/Upsert action when incoming .csv has invalid structure for specified object type

[stas-fomenko]

STR:

1. simple trigger -> dropbox (or any other component that could pass csv attachment to next step)
2. csv for step2 (it has invalid structure, required Name field is missing):

Name123123,Description
TestAccount Stas,Description

3. step3 -> Bulk Create/Update/Delete/Upsert action: selec create operation, account object, some small timeout (5-10-20sec)
4. Retrieve sample

AR:
Request Timeout and uncaughtException, logs:

Starting your Docker container ...
[INFO  tini (1)] Spawned child process '/run.sh' with pid '6'
Starting application in apprunner...
node: /usr/lib/libstdc++.so.6: no version information available (required by node)
node: /usr/lib/libstdc++.so.6: no version information available (required by node)
Will try to start app at /home/apprunner
node: /usr/lib/libstdc++.so.6: no version information available (required by node)
node: /usr/lib/libstdc++.so.6: no version information available (required by node)
node: /usr/lib/libstdc++.so.6: no version information available (required by node)
node: /usr/lib/libstdc++.so.6: no version information available (required by node)
node: /usr/lib/libstdc++.so.6: no version information available (required by node)
node: /usr/lib/libstdc++.so.6: no version information available (required by node)
invokeModuleFunction – init is not found
Checking if incoming messages is lightweight...
Going to check if incoming message body is lightweight.
No object id header so not lightweight.
Empty headers so not lightweight.
Going to check if passthrough for step is lightweight. { stepId: 'step_2' }
No object id header so not lightweight.
Checking if incoming messages is lightweight...
Checking if incoming messages is lightweight...
Going to check if passthrough for step is lightweight. { stepId: 'step_1' }
Starting Bulk insert action
Going to fetch secret
Got secret
Job error
process.uncaughtException
[INFO  tini (1)] Main child exited normally (with status '1')

AR: error thrown, so user may understand what is gone wrong