Prerequisites
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.
Support and Limitations
- Triggered Tasks support the following HTTP Methods:
- GET
- POST
- DELETE
- PUT
- PATCH
- HEAD
- The Open API specification (also known as Swagger) is supported. You can download your Triggered Tasks in API form in SnapLogic Manager > Assets.
- The Cloud URL has a 15-minute connection limit regardless of whether the connection is idle or not, so it should not be used for Tasks that stream data in or out beyond that time period.
- A Snaplex consists of multiple nodes. If the Triggered Task is set to run on a Groundplex (also known as an On-premises Snaplex), options for Task URLs include one that is reachable from the Cloud (Cloud URL), and others that are limited to the on-premise network (On-premises URL and an Override URL).
- You cannot run a Triggered Task if using the Cloud URL with a password or the bearer token if the Task owner's password is expired. Likewise, using the Cloud URLs. If Ground URL with expired credentials fails the execution with a 307 error. The only exception is that if you trigger a Task (whose owner's password is expired) using the Ground URL with the bearer token, then the Task runs . However, using the Ground URL with expired credentials fails the execution with a 307 errorsuccessfully.
- When you access the URL for a Triggered or Ultra Task that is in an Org different from the one you last selected, SnapLogic Manager displays the Task details, but the Org does not automatically change to the one that owns the Task. Use the selector at the top right in Manager to switch to a different Org.
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.