dtujo2022
Member
I have an Orchestration that gets called from a External Application (Windows Service) that receives parsed EDI data in json format. The Orchestration has one object in it, a Logix Extension. All this logic extension does is transforms some data and then performs two inserts into two custom tables. Normally this orchestration take 0.3 seconds to run, but randomly it takes 90.3 seconds or 180.3 seconds to run. I know it is happening before the inserts because the audit fields I have in the tables are consistent with when the Orchestration finished running via Orchestration Monitor Run Details. At first I thought there could be something wrong with the data being passed in, so I singled out a call that took 180.3 seconds to run and manually called the Orchestration using the same json data and it ran in 0.3 seconds with no issues. It seems I can only force the long running Orchestration when I run the window service on many files (50+). It seems after several iterations of running the Orchestration is when it seems I'll see cases where the Orchestration took extremely long to run. What is weird is that it is always either 90.3 seconds or 180.3 seconds. I believe it has to be a business function because that is the only thing that is happening in the LE before the inserts. The business functions that are being called are B0000580 and N0800640, but numerous times. Because I am calling this Orchestration numerous times in a small time frame and each Orchestration is calling those two BSNF numerous times in each call, am I crashing something or causing something to time out?
