Error Handling in SnapLogic - InterWorks
Hello We have a blog post posted on the topic Error Handling and Best Practices on our website which i am sending the URL below. We cover most of the stuff you need to know about error handling and what are the best practices to implement in the pipelines for the error handling. Please be free to leave a feedback in the comments section and if you have any further questions you can contact me. https://interworks.com.mk/error-handling-in-snaplogic/How 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 Meitei
Reference 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)
