Gruss Forum • View topic - API-ERROR Anyone....?

by **GaryRussell** » Thu Feb 28, 2013 3:03 pm

See http://gruss-software.co.uk/forum/viewtopic.php?p=40700

by **llama** » Thu Feb 28, 2013 3:07 pm

This was placed on some random Forum a couple of days ago......

http://community.welldonesoft.com/troub ... /msg17430/

by **Pawcias** » Tue Mar 05, 2013 5:32 pm

GaryRussell wrote:Definitely something going on with the API. I am currently getting BBM_DAEMON_NOT_AVAILABLE if more than 5 below minimum stake bets are placed at the same time.

If you are using the Beta version (1.1.0.66x84 or above) then there is an option to specify the batch size requested. This could serve as a temporary workaround. When setting up the link to Excel set the "Below minimum stake batch size" to 5 and let me know if this helps.

Hi,

I have problems last times with updating bets. When i have two bets on the same price, lets say two bets at lay 4,5 and I want to update them to 4,6 price, one of these bets dissapears. I have also quick comunicate down with red letters and black background: Update bet error: BBM_DAEMON_NOT_AVAILABLE.

Its make trading with tick offset very difficoult especially when tick offset fires in parts.

I am using 1.1.0.65z9c BA version.

by **GaryRussell** » Tue Mar 05, 2013 5:56 pm

Pawel wrote:
GaryRussell wrote:Definitely something going on with the API. I am currently getting BBM_DAEMON_NOT_AVAILABLE if more than 5 below minimum stake bets are placed at the same time.

If you are using the Beta version (1.1.0.66x84 or above) then there is an option to specify the batch size requested. This could serve as a temporary workaround. When setting up the link to Excel set the "Below minimum stake batch size" to 5 and let me know if this helps.

Hi,

I have problems last times with updating bets. When i have two bets on the same price, lets say two bets at lay 4,5 and I want to update them to 4,6 price, one of these bets dissapears. I have also quick comunicate down with red letters and black background: Update bet error: BBM_DAEMON_NOT_AVAILABLE.

Its make trading with tick offset very difficoult especially when tick offset fires in parts.

I am using 1.1.0.65z9c BA version.

Sorry, but you will have these problems with the version you are using because the API problem still exists. You should try the Beta version and our workaround of setting the batch size to 1. See http://www.gruss-software.co.uk/forum/v ... 3&start=15

by **Pawcias** » Tue Mar 05, 2013 7:47 pm

Thanks , I installed Beta version but dont know how to change batch size.

I also tried Fairbot and i saw that it allows for only 4 bets at one time (placing or updating). So if you trying to place 10 bets at one time on in-play football market then you wait 8 seconds with first 4 bets, another 8 seconds with next 4 bets and the last 8 seconds with last 2 bets (placing or updating). So iI dont but maybe 4 should be this maximum also in Betting Assistant.

by **Pawcias** » Tue Mar 05, 2013 7:50 pm

So I dont know what causes these problems but maybe "4" should be this maximum also in Betting Assistant.

by **Pawcias** » Wed Mar 06, 2013 10:18 am

I only use a ladder but I found the option to change the batch size and unfortunately it does not affect the trade ladder. Even when I open the same market at the same time excel and ladder.

by **GaryRussell** » Wed Mar 06, 2013 1:47 pm

Pawel wrote:I only use a ladder but I found the option to change the batch size and unfortunately it does not affect the trade ladder. Even when I open the same market at the same time excel and ladder.

The workaround has only been implemented for Excel bets so far. I will implement the same for manual bets asap.

by **N Counter** » Thu Mar 07, 2013 4:59 pm

I'm curious, how close in time can bets be submitted without be considered as the same batch? For instance if 10 bets were fired off in half, quarter... of a second, would they be in the same batch?

by **GaryRussell** » Fri Mar 08, 2013 3:37 pm

N Counter wrote:I'm curious, how close in time can bets be submitted without be considered as the same batch? For instance if 10 bets were fired off in half, quarter... of a second, would they be in the same batch?

No they would not be in the same batch, but I am currently trying to determine if simultaneous batches have the same problem.

by **Pawcias** » Mon Mar 11, 2013 4:33 pm

Hi Gary,

I belive you didnt forget about workaround for ladder trading but just in case...

Possibilty of setting batch size to 1 would fight BBM_DAEMON_NOT_AVAILABLE error while updating more than 1 bet on the ladder. Without it some bets disappears while updating them from same price.

by **Castillo** » Fri Mar 15, 2013 2:43 pm

GaryRussell wrote:The API problem still exists. You should try the Beta version and our workaround of setting the batch size to 1.

Hi Gary

Any further news on this? Is it still advisable to keep the batch size setting to 1 for both placing bets and using the UPDATE trigger.

Thanks
Castillo

by **GaryRussell** » Sat Mar 16, 2013 9:51 am

Betfair are working on a fix which should be implemented shortly. I still recommend setting the batch size to one for the time being.

by **Pawcias** » Sat Mar 16, 2013 1:39 pm

I guess Gary You will not make any "beta" solution for ladder traders until Betfair resolve it?

by **GaryRussell** » Sat Mar 16, 2013 2:26 pm

Pawel wrote:I guess Gary You will not make any "beta" solution for ladder traders until Betfair resolve it?

I will still provide this feature as soon as I can.

API-ERROR Anyone....?

Who is online

Sports betting software from Gruss Software