1 | Client uses the Cloud URL to trigger the API call against the control plane over an HTTPS connection |
2 | The Pipeline is prepared and starts running on the Snaplex JCC node over the WebSocket for the input data and output stream. |
1 | The client triggers the task via the on-premises load balancer URL. |
2 | The load balancer chooses the Snaplex JCC node to run the pipeline. |
3 | The request is sent to the control plane for pipeline preparation. |
4 | The control plane chooses the Snaplex JCC node based on pipeline load, then sends the request over WebSocket. |
5 | Streaming data is sent over HTTPS connection. |
Type | Advantages | Disadvantages |
---|---|---|
Cloud Triggered Task |
|
|
Ground Triggered Task |
|
|
This workflow represents actions taken by both SnapLogic Org admins and users.
You must have permissions to Project Space and Project to create and update Triggered Tasks
You must have a Cloudplex or Groundplex set up to run a Triggered Tasks successfully.
Since the connection to the client has a 15-minute timeout, long running Pipelines invoked as Triggered or Ultra Tasks through a Cloudplex URL might not complete before the timeout occurs. For Groundplex users, this timeout does not apply to the On-premise URL.
When you create a Triggered Task and change the Run Policy to Scheduled, the Triggered Task URLs are not disabled. Therefore, the underlying pipeline is still executable through the Triggered Task URLs, even though the Task is now a Scheduled Task.
Workaround: create a new Scheduled Task asset referencing the target pipeline and disable or delete the Triggered Task.