Am getting same error also and file then disappears into ether. Anybody a response to a solution maybe? Thanks Mike
Can you try and read the file with a File Reader instead ? If you can’t read the file or the file reader throws an error like ‘File not Found’ then most likely the path to that file is incorrect.
@j.angelevski Yep I already have a file reader previously working successfully in a upstream pipeline- it reads ok everytime.
I am trying to move upto 2 .csv files. Its a simple archive business objective after the files have been processed.
The error seems to be consistent when I have 2 files and one of the files has no data (a valid business scenario). It always errors on the no data file (a file with just headers present in the csv).
BUT if I run the pipelines so targeting only that empty data file (so only processing 1 file) then I get no error at all and the same file is successfully moved to the correct archive folder.
If I run for the 2 files scenario BOTH WITH DATA in them, then no errors and both files get archived into there respective target folders.
But the file operation snap error stack trace is like above in the original post, when it happens.
Am totally baffled now.
Do you have the “Error if exists” property enabled by any chance ?
This would cause the snap to fail if the file already exists in the target location.
