Only on adding merge node after upload b2b and fashion cloud throws error, but when the merge node is deleted and directly giving input from B2B and fashion cloud to split in batch running the workflow but we are not getting teams notification on completion
It is possible that it is related to your workflow but I would still like to know if you are in queue mode, When you are on queue mode the workers would trigger the workflow not the main instance like when you press the run now button so knowing this would help rule out any issues there which is why we ask
Quick edit… The new message you have shared would also have been handy to have in the original post along with the rest of the template we request.
There are no steps to check, When you set up n8n in AKS and you created the configuration files did you set it up to run in queue mode. It would have involved setting EXECUTIONS_MODE to queue and configuring Redis.
I have also had your workflow running on my local instance and it appears to be ok, So it could be that something has gone a bit strange with your local copy.
Looking at the workflow again that merge node does seem oddly placed and I am surprised it works at all as it is waiting for both inputs before moving on so I would expect that to possibly cause some issues but if it is ok from execute in theory on a schedule it would be ok as well.
As you are in queue mode it could be worth making sure all of your workers are on the same n8n version to rule out anything odd there, It might even be worth checking the worker logs to see if they show any errors.
Thanks worker node was never updated and still had 0.214 version where the deployment had the latest, updating the worker to latest fixed the error.
Can you also tell is there any other way to place the merge node or merge node not needed at all, since you said its oddly placed?
Here both will have input because all the files input in “split in batch” to upload in both B2B and fashion cloud and the loop continues, once the last batch ran and done in “split in batch” we are sending teams notification