So can anyone tell me why it seems so slow to sequentially walk through and import data from another DB? 32 min for 50 Orders with a total of 118 Lines.
Any advice on possible reasons why would be appreciated.
It depends a lot on how you are building the workflow, how the source data is getting assimilated. Then there are the idiosyncrasies of the workflow itself, it can be tricky to track it down without seeing the workflow and the environment in detail.
A couple of tips that have helped me:
- Do you have sequential in your input channel set to no? If so try setting to yes.
- Looking at the activity details in the Document tracking to help nail down which part of the workflow is slowing things down.
I am sure there are others that have an opinion, but ESC is one of those things you love it and live in it, or hate it and use any trick available to avoid it. 
1 Like
I agree with Simon. Use Document Tracking to drill down into the records/calls that are taking the longest time. You should be able to see if there is an Epicor BO call that is taking extra long. 118 Order Lines in 32 minutes averages out to about 16 seconds per line. That seems really long, but the Sales Order BO does a lot of background processing when orders are entered and any BPMs you have might also slow it down. I’ve also had imports take longer if/when there is an error, even if the record is able to process.
I’m very much in the camp of “get it working and don’t touch it except to monitor.” Now that we’ve upgraded to 10.2.600, I have it on the back burner to look at scheduled Epicor Functions to replace Service Connect and a couple of other services we have running.
1 Like