Background/ASync Processes occuring during/after change even
Posted: Wed May 07, 2014 7:48 pm
While opening a new order, testers are entering transactions, and in some cases changing the order status to "Closed" all before the initial save of the order.
Our service is receiving a change event and invoking the API, but the Ledger Balance is calculating as 0.00 and Date Closed is not calculated. Subsequent saves to the order which trigger add'l change events seem to process correctly.
Is it possible that the change event for the initial save is happening during some type of background process or async processing which is still occuring by the time we grab the order?
If so, do we need to delay in order to allow these processes to complete before invoking the API?
Thank you.
Keith
Our service is receiving a change event and invoking the API, but the Ledger Balance is calculating as 0.00 and Date Closed is not calculated. Subsequent saves to the order which trigger add'l change events seem to process correctly.
Is it possible that the change event for the initial save is happening during some type of background process or async processing which is still occuring by the time we grab the order?
If so, do we need to delay in order to allow these processes to complete before invoking the API?
Thank you.
Keith