The SnapLogic control plane and data plane were improved to more gracefully handle certain overload conditions on a Snaplex. This change introduces a new "Queued" state for pipeline executions and adds properties to the Snaplex configuration to set the resource thresholds used to detect an overload.
When an execution is in the Queued state, the control plane will try to start the execution when resources become available on the Snaplex.
- A pipeline will not stay in the Queued state forever; it will timeout after a while. A scheduled pipeline will timeout before the next scheduled execution or 4 hours, whichever comes first. A ForEach execution expires after 5 minutes.
- Not all methods of execution will result in a pipeline being put into the Queued state. Only executions started by a Scheduled Task or a ForEach Snap.
Pipeline executions started by the Designer will fail immediately if the Snaplex is overloaded so that you are alerted of the overload. Triggered Task executions will 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.