Forum Discussion
An Exit snap doesn’t write to the error view, so it’s going to cause the pipeline to fail when it fails. The Error Pipeline is only there to catch documents that snaps write to their error views. Sorry, that’s kind of a subtle distinction.
I’ll try to elaborate a little more. When an Error Pipeline is attached to a pipeline, any snaps that are set to stop the pipeline execution when writing to the error view will instead pass the error document to the Error Pipeline. Since this is the default mode for snaps, your error pipeline should already be receiving errors without having to add any Exit snaps. You would only want to add an Exit snap if you really wanted a pipeline to stop instead of continuing in the face of errors.
Thanks a lot for your answer
I get the difference between the error view and the exit Snap.
Everything is clear.
Thanks again.
Stéphane
- dmiller7 years agoFormer Employee
Because preview only displays the first 50 records pulled (or 8k for binary files), several factors may impact what displays.
- as @akelpe suggested, look to see what might be filtering records out.
- Is the data coming through dynamic? If so, that may be one reason why you may see varying results.
- Your browser caches your preview results. If you are finding your preview data is not exactly what you are expecting, click Retry next to validation.
See Data Preview from a Pipeline in our documentation for more information.
- akelpe7 years agoFormer Employee
Is it possible that you have a filter that simply filters out all results?
- maheshpraut7 years agoNew Contributor
well the records are passing right through the pipeline , pretty much with desired outcome, but the validation simply does not show the output of each snap. Validation output for some snaps like rest get does appear at times and let say not with others like data mapper everytime.
I have shown it our teams internally, and they are equally surprised with this behavior. The problem takes a different shape when I remove some of the other snaps in pipeline, then suddenly some of the ‘not outputting snaps’ now start showing the output, but thats again not for all snaps.
This is simply spiking up my development time by , may be 5x .
- tarena4 years agoNew Contributor III
Not to ressurect the dead, but I am having the exact same problem as OP. I’m validating a pipeline, the pipeline statistics are showing documents moving through, but the UI doesn’t show any sample documents or the buttons to view sample docs. Was there any resolution on this thread?
- steffeck4 years agoNew Contributor II
Did anyone find a solution? I also do not see any preview anymore. I check with other team members and they have the same.
I just do not get any preview icon anymore.- mbowen4 years agoEmployee
Sorry Tom for not replying sooner. There may be an issue here. I’m helping zero in on this problem. I may ask both of you to create a support ticket to help escalate this issue, but first want to get feedback from some of our other dev teams. I’ll update this thread today.
- mbowen4 years agoEmployee
There has been a recent issue with pipeline validation not showing preview data for a customer which was fixed by restarting their node. There may have been some file system attention too. I would suggest creating a support ticket to resolve this.
Related Content
- 4 years ago
- 2 years ago