Performance with Triggered task

[abinayad]

As part of our project requirement, we are using Triggered task and observed that performance is not as expected.

So, can someone help to understand whether the trigger task has some latency in general to complete the transaction?

[tlikarish]

Nope – since a Groundplex runs on a customer’s infrastructure it is not bounded by any limitations.

[bhavani]

Hi,

In our pipelines we are using less snaps which expected to complete in less than 10 sec but we observed it taking more than that. We also observed it taking expected time whenever we run it manually. We are using Cloud URL and some times Load balancer URL for triggering. The Pipeline running on Coudplex.

[sanjaynayak]

@tlikarish thanks. Tested it out both ground and cloud with applying policies, it is working as expected.

[sanjaynayak]

@tlikarish , As part of bulk amount of request submit for trigger task, response is coming like you can’t run one more request since existing request is already running, in this case 2nd request is going to be queued or rejected.

In case we are disabling this option, we are getting response like you can’t run current request more than 10 for org limit, how to increase org limit over here.

Any suggestion will be helpful.

[tlikarish]

sanjaynayak:

@tlikarish , As part of bulk amount of request submit for trigger task, response is coming like you can’t run one more request since existing request is already running, in this case 2nd request is going to be queued or rejected.

This happens when the task has the property Do not start a new execution if one is already active selected.

sanjaynayak:

In case we are disabling this option, we are getting response like you can’t run current request more than 10 for org limit, how to increase org limit over here.

This should only be applicable to cloud triggered tasks. Could you verify that you’re doing a ground url or secure ground url.

For more information on the API Limits check out this documenation.