I can see there was a delay, but I don't see an error message for why, which is kind of strange to say the least. The only thing that would make sense is if we lost contact with pricing sources or if we didn't have enough SBD to fill the order at the time it came in and then manually fixed it later. I think this is probably what happened.

But either case should normally generate an error message, and I don't see one. Maybe some recent change to the code cleared the error when the order was re-processed, so we'll investigate further.

Sorry for the delay in any case.