All right so maybe if that is not possible (creating one queue) I suggest to build technical robot to merge those queues into one. His job would be to:
Get transaction item by reference (correct me if I’m wrong but i assume you need specific data from each queue. I am guessing you cannot just get first item from each queue). First queue will not have filter transaction, but next should do.
If first queue is empty then robot will stop. So you have to decide which one is checking first.
In process.xaml you can check data, maybe pre process it and etc. If everything is ok then add transaction item with all the needed data to 4th queue. This would be used for right process. Remember that all of the transaction items have to be updated to success. If sth is missing (for example transaction item no 2 is empty) then you can create bool variable with true value (bool_postponed). If so in settransactionStatus.xaml you can add sequence to change status not empty transaction items to postponed.
In that technical robot you shouldn’t have app exeption - if you build It right. You can create some business exceptions scenarios based on data manipulation (checking if data is correct and no missing) though.