...
SnapLogic imposes throttling on pipelines Pipelines executed through a triggered task Triggered Task. The API throttling is done on Groundplex Groundplexes and Cloudplex Cloudplexes for triggered pipelines Triggered Tasks initiated against the Cloud URL; on-premise URL requests are not throttled. There are no limits currently on pipeline executions Pipeline executions initiated in any other manner (like scheduled pipelinesScheduled Tasks). There are no limits currently on processing requests through Ultra Pipelines, which are recommended if the number of API requests is expected to be very high.
There are two limits for triggered pipelinesPipelines:
- Total API limit (per day): This is the total number of triggered pipelines Pipelines which can be executed per day. The count is reset to zero at midnight UTC.
- Concurrent API limit: The total number of triggered pipelines Pipelines which can be concurrently executed. The default is 10. A triggered pipeline Pipeline counts against this limit until the pipeline Pipeline completes.
Hitting either of the above limits will cause the next triggered pipeline Pipeline execution to fail with HTTP status code 429 (Rate limit exceeded). Currently-running triggered pipelines will continue Triggered Tasks that are running continue to do so, and non-triggered pipelines Pipelines can be started without issues. If the limits need to be increased, contact your SnapLogic Account ManagerCSM.
API Usage Detail
Click API Usage Detail to display reports on API user activities and monitor the API requests. These reports provide visibility into the top ten triggered tasks Triggered Tasks (API calls). You can scroll through a table of API usage statistics: Number of API calls, Task Name, Project, and Task Owner. For quick reference, a pie chart summarizes the number of API calls made (broken down by task name) against the remaining number of available API calls. You can also switch between Daily (which allows you to select the day) and Concurrent views.
...