The SnapLogic control plane and data plane handles certain overload conditions on a Snaplex, including a Queued state for Pipeline executions. When an execution is in the Queued state, the control plane will try to start the execution when resources become available on the Snaplex. You can also configure an Alert/Activity Notification for Snaplexes to set resource thresholds that detect congestion.
- A Pipeline does not remain in the Queued state indefinitely and times out after a while. A scheduled Pipeline times out before the next scheduled execution or 4 hours, whichever comes first.
- Not all methods of execution result in a Pipeline being put into the Queued state. The Queued state applies only to executions started by a Scheduled Task.
Pipeline executions can fail immediately if the Snaplex is overloaded; this condition triggers the alert notification if configured. Triggered Task executions retry for a minute before returning a failure to the requesting client.
Slot allocation is configured per Snaplex. See the Update Snaplex dialog for these options.