FTP Adapter Is Raising Different Error In 17.3.3.

(Doc ID 2299258.1)

Last updated on SEPTEMBER 01, 2017

Applies to:

Integration Cloud Service - Version N/A and later
Information in this document applies to any platform.


On : NA version, Core Issues

FTP adapter is raising different error in 17.3.3.

scheduled flow that runs every night to process a file. I use FTP adapter read file as the first step of my flow to read the file and process it. Some nights the file may not be present. If the file is not present, then the flow used to fail with "No file to process" error. FTP adapter used to raise the error. I wanted to suppress that as an error. So I defined a global fault and in the fault I put a switch statement where if the error was "No file to Process" I gracefully exited. It worked fine in 17.2.5. In 17.3.3 the FTP adapter is raising a new error

OSB-380001Error while translating.
Translation exception.
Error occured while translating content from file /u01/data/user_projects/domains/test_domain/6/fileftp/temp_ftp/-957461960/outbound/At3Zpz9+I7Iyqn6wjYyvo09xNN_bTgrrsmDJsS4GjTA=.
Please make sure that the file content conforms to the schema. Make necessary changes to the file content or the schema.
:Application ErrorRouteNode1response-pipelineSyncReadFile

Customer has no way to capture the file not found exception. This error can occur for genuine cause and hence I can't ignore it.

Requested outcome:
Either provide a mechanism in FTP adapter to ignore if no file is present or bring back the old error.
This is a flow in production and we can't change production flow for every small little behavior change for every release.

The issue can be reproduced at will with the following steps:
1. create Flow and Test: (see iar)


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms