Error management on JMS Consumer
Hello everyone, We are currently trying to improve our pipelines by adding error paths and are having problems with the JMS Consumer snap. Unlike other snaps, like the SQL Server snaps, where a connection failure is routed to the error path, a connection error on our JMS snap does not trigger the error path and fails (see attached image). Is there a way for us to catch those errors without ending with a failure ? Please note we do not use ultra pipeline/ultra tasks, but a regular schedule task to run this pipeline. Edit for clarity : Error is not triggering error path Here same type of error (connexion error) is triggering error path (don’t mine the failure on the next box it was expected here)Solved12KViews1like17CommentsError occured while creating a mount smb:///
I am encountering a error with my file writer snap while trying to write to a file share on a different server. The error is as follows: Error occured while creating a mount smb:///. I dont think this is a permissions issue as I have granted access to the account I am using on the server I am trying to write to. That got me past an access denied error that I had encountered earlier in testing. I am also open to any suggestions you may have to help me better troubleshoot. Thank you for any help in advance, it is greatly appreciated!8.6KViews0likes9CommentsThrow error to trigger error pipeline
Hello, I’m wondering if there is any way to trigger the error pipeline, without having to execute it with a Pipeline Execute snap. The idea is that I filter for Client or Server errors, which i’d like to handle differently based on the error code and in case of an internal server error, simply throw it to the error pipeline to log the error and create a ticket. Does anyone have an idea of a good way of throwing the error to the error pipe without explicitly triggering it through a Pipeline Execute snap? Best regards ThomasSolved5.6KViews0likes4CommentsError Handler for Validation
Submitted by @stodoroska from Interworks This pattern should be called as an error pipeline and stores all the error records in to a csv file. Configuration Parent pipeline should be made that will invoke this as a error pipeline. Target location is pipeline parameter. No need for changes in the code. Sources: Pipeline that will call this pipeline and will send JSON-formatted data Targets: CSV file on the file sharing system Snaps used: Mapper, CSV Formatter, File Writer Downloads Error Handler for Validation.slp (7.2 KB)5.2KViews0likes4CommentsHow to get JSON node which cause Workday webservice error under Workday Write response message?
Hi Everyone, In SOAP UI/ Workday Studio’s SOAP response, we usually get Web Service(WS) error xpath which tell us the node/XML xpath cause webservice error. This xpath allow developer to understand which section of WS request cause the error. Example of SOAP response having error: wd:Validation_Error wd:MessageInvalid ID value. ‘BUSINESS ASSE’ is not a valid ID value for type = ‘Location_Usage_ID’</wd:Message> wd:Detail_MessageInvalid ID value. ‘BUSINESS ASSE’ is not a valid ID value for type = ‘Location_Usage_ID’</wd:Detail_Message> wd:Xpath/wd:Put_Location_Request[1]/wd:Location_Data[1]/wd:Location_Usage_Reference[1]</wd:Xpath> </wd:Validation_Error> Similarly, I am looking for specific node which cause any webservice error when Snaplogic’s Workday Write snap execute. Unfortunately, current Workday write does not give such node details in SOAP request that causes WS error. Getting such JSON node or Xpath location will help my business scenarios which needs to identify specific address section that causes WS error for Put_Student_Application. Under this web service, Workday allows us to add different types addresses related to student including friend and family (like, mailing, permanent, parent address etc.). Below is error message of Workday Write: From above error message, we are able to get error description and suggested resolution but it does not give any information regarding which address section (either personal mailing, permanent, parent address etc) cause said WS error. Kindly advice if anybody came across such scenario and how we can handle such cases. Regards, Sandeep Meitei4.8KViews2likes3CommentsReference Implementation - Integration Pattern - Error Handling and Retry Pattern
Error Handling and Retry Pattern This pipeline capture errors thrown by error view and invokes an error pipeline. The error pipeline captures the exception encountered and records all the data relating to the execution (Snap level and pipeline level) into a database schema. One could potentially use a database or Kafka or any JMS-compliant queuing mechanism to log the errors. Video Pipelines Attached Error Handler Pipeline_2018_06_25.slp (28.8 KB) Retry Handler_2018_06_25.slp (29.8 KB) The following are error-prone pipelines for use in testing the Error Handler pipeline. Pattern 1 - Step 1.0 - Oracle to Redshift Parent_2018_06_25 (1).slp (8.7 KB) Pattern 1 - Step 1.1 - Oracle to Redshift No Shredding_2018_06_25 (1).slp (24.4 KB) Pattern 1 - Step 1.2 - Oracle to Redshift Shred_2018_06_25 (1).slp (8.3 KB)4.6KViews1like0CommentsHow to stop Parent Pipelines
Hi, I want to understand how an error on a child pipeline impacts the parent. We have a parent pipeline calling a child pipeline with a pool size of 1 so that it processes a series of sql scripts in sequence. I also have an error pipeline which writes the erroneous sql script to a log before passing to an Exit snap which forces the pipeline to terminate. Both the Parent and Child pipelines reference the same Error pipeline. What I expect is that if an error occurs in the child pipeline then it will pass to the Error pipeline and exit the child. Furthermore that should result in the parent Pipeline Execute snap receiving an error which throws to the error pipeline and the parent pipeline will exit as well. So basically, if an error occurs, stop everything. However what I get is that an error occurs in the child pipeline and it stops, but the parent pipeline continues on as if nothing happened. How can I get the parent to stop when the child does?SolvedAPI responses not working
Hello, So I created an API specification with these error responses. ‘400’: description: Bad request. ID must be an integer ‘401’: description: Authorization information is missing or invalid headers: {} content: {} ‘404’: description: Not found ‘500’: description: Interal server error (500) When I uploaded the spec into snaplogic and changed the pipeline I want it to fetch data from SQL server select with given ID. I want to reroute the error when the ID is not found. But when I do that I still get on the API call the Server error 500 form the snap itself of snaplogic and not from the reroute or from the specification defined error response Does someone know why it does not reroute the error to my custom error view or the response code from my api specificationSolved3.7KViews1like4CommentsError view gets executed without an error
Hello, While using rest post snap, I have error view enabled. Snap runs without any error, but still error view gets executed. Error view updates a file in JSON format. My goal is to update the file only when I get error. Thanks for you time, SmitSolved3.5KViews0likes2Comments