Catch file reader error and use dummy file instead

[ijoel92]

By reading another post from 2016, it seems the file reader (and excel reader too) fail if the configuration is incorrect but is not caught by the try/catch. They resolved it by checking if the file exists, but what if the file exists but has a different format? What is the correct way of catching that configuration error?

Problem getting error trapping to work to trap 'file not found' for file/csv reader nodes

I have a work flow where I want to check the content of an existing csv file. Complication is that, at the first time of writing, the file would not exist. In this case it is created later on by the workflow and will thenceforth be available for checking in this way. I can think of a work around but would have liked to use error trapping to handle this gracefully and pipe in some dummy data in the case of file not found. I don't seem to be able to make this work however, the csv reader node stil…