On this Page
Resumable Pipelines suspend the flow of data when an endpoint is down. In Resumable Mode, Pipelines are suspended instead of failed when an error is encountered, and Pipeline status is displayed on the SnapLogic Monitoring Dashboard. As such, Resumable Pipelines are fundamentally different in execution than standard Pipelines. In a Resumable Pipeline, every Snap runs to completion before any of its output documents are passed to the subsequent downstream Snap. Whereas in a standard Pipeline, a Snap outputs a document, which becomes the input to the subsequent downstream Snap even before the first Snap completes its document processing.
Executing a Resumable Pipeline saves the state of the Pipeline when hard exceptions occur and allows you to resume the Pipeline, running the original version of the Pipeline at the point of failure and not the latest version. Documents that have been processed successfully by a given Snap are not re-run.
With Resumable Pipelines, you can now achieve exactly-once-delivery. The Snaps in the Suspended Pipeline that have executed before suspension are green, while those Snaps that are yet to be executed turn orange.
Your Org must be subscribed to Resumable Pipelines to use this feature.
In SnapLogic Designer, select the target Pipeline and open the Properties menu. You can enable Resumable Mode in existing Pipelines.
By default, the Error Pipeline option is disabled and incompatible with Resumable Pipelines. |
In SnapLogic Designer, if Snaps in your Resumable Pipeline turn orange, then your Pipeline is suspended. You can also configure a Task to send an email when it goes into the Suspended state. To view status of a Resumable Pipeline, go to the Dashboard.
The Status column displays the following additional states for Resumable Pipelines.
You can resume suspended Pipelines after the endpoint is restored by selecting the Pipeline and clicking the Resume icon (). If you click the Stop icon (), then the execution state is deleted from the nodes and that execution is no longer be able to resume. Additionally, you cannot manually suspend a Resumable Pipeline.
The Resumable Pipeline feature is best implemented along the lines of the following use case.
The following pipeline is an Ultra Pipeline with the Pipeline Execute Snap, which calls the Resumable Pipeline.
This parent Pipeline calls the following Resumable Pipeline, where two concurrent services are processing documents to be joined together and mapped.
An error occurs in one of the Snap, so the remaining Snaps, which have not been executed, turn orange to indicate their suspended state in the Pipeline.
The Dashboard shows one error document in the parent Pipeline indicating that an error occurred.
The Extra Details tab includes a history of states for the Resumable Pipeline.