This is a production issue. We have a Trading Partner where the delivery methods is queue for polling using the built in EDI Batch process. I’ve confirmed that the documents are processed and queued for delivery. When I manually execute the service “wm.tn.queuing:listQueuedTasks” there are pending tasks in the list.
However, when I manually execute the service “wm.tn.queuing:deliverBatch” with the queue name, the documents are not dequeued and processed further for delivery.
Any ideas why this would happen?
I thought this is supposed to cause the IS to grab all queue tasks and batch them into a single X12 envelope for further processing.
Hopefully, it is Schedule delivery not Queue for polling.
In case of schedule delivery please check the Queue configuration for the Required parameters like
Sender and receiver details are correct along with SingleOutput is selected.
It will be helpful if you share the snapshot of the Queue configuration.
This queue hadn’t been touched in several upgrade cycles.
It appears that when we needed to making changes to the queue this time, all the original settings were cleared without our knowledge as we saved the queue.
I ended up having to get a restore of the system from years ago (amazing they still had it) in a sandbox server to determine the previous settings. Once I put them back in, everything worked fine.
When I went to make schedule changes to the queue the setting were deleted by accident and I didn’t notice. I had to restore the configuration from before the deployment to production and it worked.
