How to hard stop the execution of pipe line or a task
Hi, Pipe Line Summary :- I have a Parent pipeline which will browse the sftp location and pass the file information to the child pipe line. The child pipeline will read these files and generate the XML and then using the rest call these XML’s will be sent to another system. Here i want to stop the execution at 2 levels when ever an error occurs. when the snap fails :- when ever we get the error then we are calling the global error handler pipeline. the error pipe line will write the log ,creates jira ticket and sends email also. Once we do these operation i want to stop the pipe line execution. How to achieve this. When the rest snap fails :- for example when the rest post fails due to the server down or any other reason then i want to stop the execution of the entire pipeline or the task. Thanks.3.2KViews0likes2CommentsError 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.6KViews0likes9CommentsHow to access error view document
Normally with our pipelines, if there is an error, we feed the error view document into an email, or a Jira object We have had a third party create a pipeline recently, and they have not done this We have had an error over night, and this is telling me to open the error view document, and I found a post online that suggests you can do this from the pipeline, but doesn’t give any details, and I can’t find anything in Snap Logics help, or anything else online Is this possible? And how do I do it? Thanks2.2KViews0likes1CommentError Handling in multitple levels of parent-child hierarchy
I have a parent child pipeline hierarchy that is 4-5 level deep. In other words, parent pipeline (p1) calls a child pipeline (c1). c1 in turn invokes its child pipeline (c2). c2 then invoked its child pipeline c3 etc…etc… p1 → c1 → c2 → c3 → c4 I would like to have the error pipeline only configured for the main pipeline p1 and not have error pipeline for any other child pipelines. I expect that any error in a child pipeline would be propagated up the hierarchy till it hits the error pipeline. What I am finding is that the error is propagated only one level up and not beyond. Is that correct or is there any way I can achieve what I intend?3KViews0likes2CommentsThrow exception on 0 documents
Hi All, Apologies if this one has been asked before. There is a scenario in the current pipeline being developed where after a filter operation the number of documents returned can be 0. at this point the pipeline completes as there is no further processing to be done. I am looking for a pattern to capture this scenario so when there are 0 documents after this step in the process to throw an exception rather than fail silently. has anyone come across this issue before? Many thanks, Kareem.Solved3KViews0likes3CommentsHow 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.8KViews2likes3CommentsError 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)Solved12KViews1like17CommentsAPI 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.7KViews1like4CommentsThrow 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.6KViews0likes4Comments