How to limit number of transactions while running from orchestrator

Hi @Florent_Salendres

how to set logic to run only few numbers of transactions while triggering the job from orchestrator ?

Is it possible ?

Hello, you can use the transaction number and inside process you can limit check for every transaction is it greater or lesser them the limit
It can be done logically not via orchestrator as per my knowledge


Correct, there is actually yet no direct connection between jobs and queues (jobs are only initiating a process (containing the xaml’s) and the process itself will handle the queue logic, for example with the transaction number from ReFramework which could be used as a condition (compared to a limit set) to transit to End State.

One thing you could do is to retrieve the limit from either an asset or a Job parameter, which would add a a bit of “'configuration”.