We have a service that pulls demand into our system from our customer’s portal. Unfortunately, one of our bigger facilities is facing a 4+ hour upload time. This will sometimes cause Epicor Rest to time out leaving a lot of demand floating in the breeze.
In my EDI life, we tried to separate out processes depending on the fail policy. We architected it differently depending on if it was “all or nothing” or “take what you can and fix the rest.”
If it’s “take what you can…” then I might rearchitect the REST call to handle just one transaction at a time. Instead of loading the whole release in a single thread, split the file up into multiple files and have multiple imports going at once. Experiment with the number. Start with a number that’s similar to the sites that work. It will remove the timeout issue and maybe get that site loaded even quicker.
@josecgomez
I believe the service is using a single session, but I do not have direct information on how their program works. I will be reaching out to them for the specifics and will get back to you on that.
@Olga
I have forwarded them the link and code snippet you recommended. Hopefully, this will help.
@Mark_Wonsil
I like that! Ill see if after they have calculated out all the changes and are ready for a data load if they can make several simultaneous uploads instead of one big one.