On this Page
| Table of Contents | ||||
|---|---|---|---|---|
|
Overview
Common The common issues you might encounter with Ultra Pipelines Tasks include:
...
| Info |
|---|
Maximum TriesBy default, if the first run of an Ultra Pipeline fails, SnapLogic attempts to run it for a total of five times. However, you can configure the number of times you want Ultra Tasks from a specific Snaplex to run by configuring the maximum number of allowed retries for an Ultra task. To do so, modify the following parameter in Global Properties in Snaplex Update: |
Error Handling in Asynchronous Ultra Tasks
Ultra Pipelines require a Document type output in the Error Pipeline. The following pipeline provides an example of an error pipeline set up for error handling in asynchronous Ultra Tasks.
Ultra Pipelines require a Document type output in the Error Pipeline.
The following Ultra Pipeline provides an example of this design:
...
The following describes the setup for each Mapper Snap.
In the first branch, the first Mapper (Map - Build Pipeline…) specifies the runtime records to pull the errors from.
...
The subsequent Mapper Snap (Map Error Records) lists which errors to pass.
...
Then, the error messages are copied and sent to a specified email address and log in one branch, while in the original branch, a Mapper Snap (Map REST - Reply) defines the REST response.
...
We add a JSON Formatter (Status Output) after the Mapper with the HTTP status code format.
...
The final Mapper outputs the response as a document.