The SnapLogic Platform offers various ways to run Tasks. Because Triggered Tasks are a convenient way to give API consumers a URL to invoke a Pipeline without actually granting them access to the SnapLogic Platform, you should consider how and where the Task is executed.Regardless of the type of Snaplex set for the Task and underlying Pipeline, you can call a Triggered Task through the Cloud URL or Snaplex URL, which is the Self-managed Snaplex (Groundplex). The behavior of running the Triggered Task from the Cloud URL differs from that of the Snaplex URL. When you invoke the Triggered Task through the Cloud URL (for example, using a CURL command), the call is routed to the Control Plan, both of which are in the Cloud. If the request is successful, an HTTP 200 response is sent to the client upon completion of the Pipeline run. However, when you call a Triggered Task from the Snaplex URL, the HTTP 200 response is sent immediately, even though the Pipeline is still running. This behavior is the result of the additional network routing that occurs because the request is sent to the Control Plane from the Self-managed Snaplex
| Info |
|---|
The cloud URL for a Triggered Task running on a Groundplex does not support asynchronous Pipeline execution. |
You can invoke a Triggered Task using one of the following methods.
...
In your browser window, copy and paste the URL generated for the target Task.
Info title Authentication The external URL created for a task requires you to be authenticated with the SnapLogic servers. When using a web browser to access the URL, you might not have to provide credentials since you might already be logged into the Designer. Using other methods to request the Task URL requires you to provide credentials using HTTP Basic Authentication.
- Alternatively, you can run Tasks from a CLI using Curl commands.
...