However the orders that were stuck in the Being Delivered state .. and that you "unstuck" earlier today, did NOT send through their ANS transactions. Thus all products that should have been reported via ANS were not.
Please investigate this oversight in your "Order of Execution" (when ANS transactions are sent) and also manually send the ANS transactions that were lost due to this error.
Umm ... CTL? This issue has been going on for well more than a month. You've released three updates, pulled two back and are placing your hopes on this last one.
After all that work, all the concerns, all the posts and problems reported .. and it only warrants two sentences barely 18 words in total? I've been right in the heat of things here and while I generally pride myself on understanding what's going on, your Release Notes leave me scratching my head as to exactly what you mean.
Please edit the Release Notes and add enough descriptive lead-in, central issue and resolution commentary to make your document comprehensible to those that haven't been at your staff member's elbows for the past month. Please remember that we do not have the benefit of all your internal jargon, intimate knowledge of your code base .. and most do not even have the foggiest notion what really happened (other than they got billed a bunch of money twice .. and things are still broken).
