I’ve noticed something when running scrips in batch stage that did not happen before.
before upgrading to 4.4 when a scrip (thats was batch stage) was triggered by a transaction it would only run once after the batch of transactions are complete. But now with 4.4 if run a scrip in batch it TransactionBatch would have the collection of the transactions in the current batch but the scrip will consonantly run again for each transaction.
So previously if I had 4 transactions in a batch (like status change priority change etc…) it would run the scrip only once, but now if there are for example 4 transactions in a batch of changes it will run the batch script 4 times in a row.
Is this expected behavior?