Potential issue in retrieving an order after placing it

[Blade Runner]

Hi there,

I am currently experiencing the following issue:

[1] I place a first order in a market via RPC placeOrders
[2] I retrieve the orders in such markets via RPC listCurrentOrders

and the order is not immediately there.

It will be there after "some time".

The bottom line is that the order is not there if I call listCurrentOrders immediately after placeOrder regardless the bet will be there eventually and it ALREADY had an id following its placement.

I find it pretty weird and sort of demonstrating that the bet has to travel from somewhere is posted by placeOrder to somewhere else is read by listCurrentOrders.

Is there any requirement about how much time to wait before calling listCurrentOrders after placing an order to find it in the returned list?

[doctormike]

Order feedback

Hi Blade Runner
I get immediate feedback on orders placed from the PlaceInstructionReport response (you can find details of this in the development team's sample code). The response has "averagePriceMatched" and "sizeMatched" properties, which I capture as a string in a textbox. It's pretty instant.
With regards
Mike

[Blade Runner]

Hi Mike,

thanks for the advice: your suggestion works well to check what's the outcome of a specific invocation to placeOrders.

My need is more related to using listCurrentOrders, assuming it to be a reliable service.

In fact, the state of an order may have changed since it has been placed or it may have been changed by other calls to the API made in other threads or applications.

The fact that listCurrentOrders is not immediately in-synch when placing a single bet, remains a concern and has a significant impact on designing serious software on top of the API.