Performance with Triggered task
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 gen...
Forum Discussion
@tlikarish thanks. Tested it out both ground and cloud with applying policies, it is working as expected.
@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.
This happens when the task has the property
Do not start a new execution if one is already activeselected.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.
@tlikarish , Switched to secure ground url and it has no limit as per my observation and trigged 2k request which is working.
