Within the SF we have setup a process flow as an API webservice which is open to receive EDI files from an EDI broker. The process flow itself is rather simple, it has a start, decision and an end. The decision contains code to parse an XML file, perform some checks (for instance call a stored procedure which sends an email if invalid data is sent) and insert a purchase order (+ some logging info).
The question is:
Are the EDI messages sent to our endpoint always handled sequentially by this process flow? We have seen EDI messages being send in rapid succession, with a few thousands of a second in between messages (see image below).
The reason for this question is that we have an insert trigger that can handle both sets and individual purchase orders. However, we believe that orders sent in such rapid succession as is the case in the first 3 rows, is not handled well by the insert trigger.
Thanks in advance.
Best answer by Vincent Doppenberg
View original
