Problem with scalping servant as seen in bet angel tv video

Advanced automation available in Guardian - Chat with others and share files here.
Post Reply
JasBarrow
Posts: 138
Joined: Tue Sep 18, 2018 3:03 pm

https://youtu.be/KVJA9IAd7v4

I've made a scalping servant exactly as described in the above video at 6:52 but it seems to have a mind of its own. I started the servant and it placed a back bet at 2.2, when the back bet was matched it placed 3 lay bets in the market. I've attached the log so you can see what happened, another problem is the log is wrong! According to the log there was a 10 second gap between the back bet going in and the lay bets appearing. Thats not true, the lay bets hit the market as soon as the back bet was taken. The log also states that the back bet was killed, it wasnt it got matched and the servant wasn't stopped as the log states. This is not a one off example its happened several times as I've been using the servant.

Can anyone shed some light on this? I've attached images of the settings I used which are exactly as described in the video.

Thanks




15/11/2020 14:20:48: [AS 56] : € 2.00 Back bet placed on Defi Du Seuil at 2.2. Entirely unmatched when it initially reached the market. Ref: 216792324220 ( Fill or kill bet with 600 seconds delay. )
15/11/2020 14:20:49: [AS 55] : € 2 unmatched bet (Ref:216792301230) was killed.
15/11/2020 14:20:58: [AS 54] : Automation Servant ( a1 scalp servant ) Stopped.
15/11/2020 14:20:58: [AS 55] : Automation Servant ( a1 scalp servant ) Stopped.
15/11/2020 14:20:58: [AS 56] : Automation Servant ( a1 scalp servant ) Stopped.
15/11/2020 14:20:58: [AS 54] : € 2.00 Lay bet placed on Defi Du Seuil at 2.18. Entirely unmatched when it initially reached the market. Ref: 216792338729
15/11/2020 14:20:58: [AS 55] : € 2.00 Lay bet placed on Defi Du Seuil at 2.18. Entirely unmatched when it initially reached the market. Ref: 216792338737
15/11/2020 14:20:58: [AS 56] : € 2 of unmatched bet (Ref:216792324220) was filled before remainder was killed.
15/11/2020 14:20:58: [AS 56] : € 2.00 Lay bet placed on Defi Du Seuil at 2.18. Entirely unmatched when it initially reached the market. Ref: 216792338735
You do not have the required permissions to view the files attached to this post.
User avatar
Dallas
Posts: 23599
Joined: Sun Aug 09, 2015 10:57 pm

With regard to the extra ten seconds on the fill or kill, that'll be betfair failing to respond to the kill request in a timely manner. When Bet Angel makes a cancellation request it'll give betfair ten seconds to respond and then tries to determine whether the bet was actually killed or not based on the information it is given. So although the logging gets delayed by the full ten seconds, it could be that the bet was filled (or cancelled) almost immediately by betfair but that they just didn't return the result of the request.
This sort of issue only happens occasionally, but it's just the way the betfair API misbehaves at times.

Its difficult to know for sure but it looks like the Servant was started 3 times, did its thing but there was late reporting in the log and it grouped everything up
JasBarrow
Posts: 138
Joined: Tue Sep 18, 2018 3:03 pm

Dallas wrote:
Sun Nov 15, 2020 3:08 pm
With regard to the extra ten seconds on the fill or kill, that'll be betfair failing to respond to the kill request in a timely manner. When Bet Angel makes a cancellation request it'll give betfair ten seconds to respond and then tries to determine whether the bet was actually killed or not based on the information it is given. So although the logging gets delayed by the full ten seconds, it could be that the bet was filled (or cancelled) almost immediately by betfair but that they just didn't return the result of the request.
This sort of issue only happens occasionally, but it's just the way the betfair API misbehaves at times.

Its difficult to know for sure but it looks like the Servant was started 3 times, did its thing but there was late reporting in the log and it grouped everything up
Hi thanks,

Yes I started the servant several times in the market when I saw a opportunity for the trade to work. But it wasn't just showing late in the log, when the back bet was matched for €2, three lay bets were fired into the market totaling €6 instead of just one lay bet.
User avatar
Dallas
Posts: 23599
Joined: Sun Aug 09, 2015 10:57 pm

JasBarrow wrote:
Sun Nov 15, 2020 3:15 pm
Dallas wrote:
Sun Nov 15, 2020 3:08 pm
With regard to the extra ten seconds on the fill or kill, that'll be betfair failing to respond to the kill request in a timely manner. When Bet Angel makes a cancellation request it'll give betfair ten seconds to respond and then tries to determine whether the bet was actually killed or not based on the information it is given. So although the logging gets delayed by the full ten seconds, it could be that the bet was filled (or cancelled) almost immediately by betfair but that they just didn't return the result of the request.
This sort of issue only happens occasionally, but it's just the way the betfair API misbehaves at times.

Its difficult to know for sure but it looks like the Servant was started 3 times, did its thing but there was late reporting in the log and it grouped everything up
Hi thanks,

Yes I started the servant several times in the market when I saw a opportunity for the trade to work. But it wasn't just showing late in the log, when the back bet was matched for €2, three lay bets were fired into the market totaling €6 instead of just one lay bet.
That defiantly sounds like a sticky API then, are you using streaming or polling?
I saw yesterday a few people posting that streaming was a bit iffy during the afternoon but polling was OK
JasBarrow
Posts: 138
Joined: Tue Sep 18, 2018 3:03 pm

Dallas wrote:
Sun Nov 15, 2020 4:12 pm
That defiantly sounds like a sticky API then, are you using streaming or polling?
I saw yesterday a few people posting that streaming was a bit iffy during the afternoon but polling was OK
I was using streaming but I've just tried it on polling and having the same issue.

Looking at the log though its saying some trades are killed, which they're not because its on a 10 minute fill or kill dela, they're actually scratched which is what is supposed to happen.

But it seems that of the trades that are scratched the lay bet is then duplicated later on. {AS 77} in the log, is then duplicated 30 seconds later (at the bottom of the log) in the middle of another trade {AS79}

[b]15/11/2020 16:47:16: [AS 77] : Automation Servant ( a1 scalp servant ) Started ( Selection context: 6. Hang em High. )
15/11/2020 16:47:16: [AS 77] : € 2.00 Back bet placed on 6. Hang em High at 6. Entirely unmatched when it initially reached the market. Ref: 216805854348 ( Fill or kill bet with 600 seconds delay. )
15/11/2020 16:47:19: [AS 77] : € 2 unmatched bet (Ref:216805854348) was killed.
[/b]
15/11/2020 16:47:32: [AS 78] : Automation Servant ( a1 scalp servant ) Started ( Selection context: 3. Le Bugue. )
15/11/2020 16:47:33: [AS 78] : € 2.00 Back bet placed on 3. Le Bugue at 4.6. Entirely unmatched when it initially reached the market. Ref: 216805875344 ( Fill or kill bet with 600 seconds delay. )
15/11/2020 16:47:35: [AS 78] : € 2 of unmatched bet (Ref:216805875344) was filled before remainder was killed.
15/11/2020 16:47:36: [AS 78] : € 2.00 Lay bet placed on 3. Le Bugue at 4.6. Entirely unmatched when it initially reached the market. Ref: 216805879960
15/11/2020 16:47:36: [AS 78] : Automation Servant ( a1 scalp servant ) Stopped.
15/11/2020 16:47:42: [AS 79] : Automation Servant ( a1 scalp servant ) Started ( Selection context: 6. Hang em High. )
15/11/2020 16:47:43: [AS 79] : € 2.00 Back bet placed on 6. Hang em High at 5.4. Entirely unmatched when it initially reached the market. Ref: 216805888694 ( Fill or kill bet with 600 seconds delay. )
15/11/2020 16:47:44: [AS 79] : € 2 of unmatched bet (Ref:216805888694) was filled before remainder was killed.
15/11/2020 16:47:45: [AS 77] : € 2.00 Lay bet placed on 6. Hang em High at 5.3. Entirely unmatched when it initially reached the market. Ref: 216805891619
15/11/2020 16:47:45: [AS 79] : € 2.00 Lay bet placed on 6. Hang em High at 5.3. Entirely unmatched when it initially reached the market. Ref: 216805891620
15/11/2020 16:47:45: [AS 77] : Automation Servant ( a1 scalp servant ) Stopped.
15/11/2020 16:47:45: [AS 79] : Automation Servant ( a1 scalp servant ) Stopped.
15/11/2020 16:47:54: [Key] : Greened up 6. Hang em High by Backing 1.96 at 5.3
15/11/2020 16:47:54: [Key] : Greened up 3. Le Bugue by Laying 0.04 at 4.6
15/11/2020 16:48:37: Guardian has detected that the market is suspended
JasBarrow
Posts: 138
Joined: Tue Sep 18, 2018 3:03 pm

Dallas wrote:
Sun Nov 15, 2020 4:12 pm
That defiantly sounds like a sticky API then, are you using streaming or polling?
I saw yesterday a few people posting that streaming was a bit iffy during the afternoon but polling was OK
Hi dallas,

Sorry to bump this but I've noticed a couple more issues today when playing around with this for a few races.

In this instance the back and lay bet were placed at the same time instead of the back bet then the lay bet when the back is filled.

17/11/2020 16:06:25: [AS 27] : Automation Servant ( a1 scalp servant ) Started ( Selection context: Samoot. )
17/11/2020 16:06:25: [AS 27] : Automation Servant ( a1 scalp servant ) Stopped.
17/11/2020 16:06:26: [AS 27] : € 2.00 Back bet placed on Samoot at 2.02. Entirely unmatched when it initially reached the market. Ref: 216929045333 ( Fill or kill bet with 600 seconds delay. )
17/11/2020 16:06:26: [AS 27] : € 2.00 Lay bet placed on Samoot at 2. Entirely unmatched when it initially reached the market. Ref: 216929045322
17/11/2020 16:06:26: [G_Auto] : Modify bet persistence 216929045322 from 'Cancel' to 'Take SP'
17/11/2020 16:06:26: [G_Auto] : Modify bet persistence 216929045333 from 'Cancel' to 'Take SP'
17/11/2020 16:06:28: [AS 27] : € 2 unmatched bet (Ref:216929045333) was killed.



And in the below 2 back bets were fired in instead of one. And the log is showing they were placed 6 seconds apart even though they were placed at the same exact second.

17/11/2020 17:01:06: [AS 34] : Automation Servant ( a1 scalp servant ) Started ( Selection context: 3. Ballydorgan Jess. )
17/11/2020 17:01:06: [AS 34] : € 2.00 Back bet placed on 3. Ballydorgan Jess at 3.25. Entirely unmatched when it initially reached the market. Ref: 216932668702 ( Fill or kill bet with 600 seconds delay. )
17/11/2020 17:01:11: [AS 34] : € 2 unmatched bet (Ref:216932668702) was killed.
17/11/2020 17:01:12: [AS 35] : Automation Servant ( a1 scalp servant ) Started ( Selection context: 3. Ballydorgan Jess. )
17/11/2020 17:01:12: [AS 35] : € 2.00 Back bet placed on 3. Ballydorgan Jess at 3.25. Entirely unmatched when it initially reached the market. Ref: 216932675799 ( Fill or kill bet with 600 seconds delay. )
17/11/2020 17:01:24: [AS 35] : € 2 of unmatched bet (Ref:216932675799) was filled before remainder was killed.
17/11/2020 17:01:24: [AS 34] : Automation Servant ( a1 scalp servant ) Stopped.
17/11/2020 17:01:24: [AS 35] : Automation Servant ( a1 scalp servant ) Stopped.
17/11/2020 17:01:24: [AS 34] : € 2.00 Lay bet placed on 3. Ballydorgan Jess at 3.2. Entirely unmatched when it initially reached the market. Ref: 216932690605
17/11/2020 17:01:24: [AS 35] : € 2.00 Lay bet placed on 3. Ballydorgan Jess at 3.2. Entirely unmatched when it initially reached the market. Ref: 216932690611
17/11/2020 17:01:28: An error occurred while cancelling bets: The entire order has been rejected.
17/11/2020 17:01:28: Cancelling bets 216932690605 216932690611
17/11/2020 17:01:29: Placed closure bet on 3. Ballydorgan Jess by Backing 2.00 at 3.2


Also in all the examples I've posted there's a lot of log entries saying bets are killed when they're not.

The only time the servant seems to work properly is the first time I use it in a market. The more you use it then the more it seems to have problems.
User avatar
Dallas
Posts: 23599
Joined: Sun Aug 09, 2015 10:57 pm

It might be better if you can post the servant and i'll run it here and see what happens

In the mean time you could download and try one of the similar Servants i've posted in the shared servants section like the one below
viewtopic.php?f=58&t=15201

All the one's I post get tested to death for several days prior to upload so I know they work 100%, so if you try that and it returns any similar errors it suggests it might be a connection issue with Betfair that's causing
JasBarrow
Posts: 138
Joined: Tue Sep 18, 2018 3:03 pm

Ok thanks Dallas,

I'll do as you suggest and try one of the servants you created.

I've attached the servant, its a very basic one but like I said I just copied what was on the video exactly and this is the result.
User avatar
Dallas
Posts: 23599
Joined: Sun Aug 09, 2015 10:57 pm

JasBarrow wrote:
Tue Nov 17, 2020 7:28 pm
Ok thanks Dallas,

I'll do as you suggest and try one of the servants you created.

I've attached the servant, its a very basic one but like I said I just copied what was on the video exactly and this is the result.
Got it, i'll have a look through it in the morning and run some tests on it during tomorrows racing
JasBarrow
Posts: 138
Joined: Tue Sep 18, 2018 3:03 pm

Dallas wrote:
Tue Nov 17, 2020 7:30 pm
JasBarrow wrote:
Tue Nov 17, 2020 7:28 pm
Ok thanks Dallas,

I'll do as you suggest and try one of the servants you created.

I've attached the servant, its a very basic one but like I said I just copied what was on the video exactly and this is the result.
Got it, i'll have a look through it in the morning and run some tests on it during tomorrows racing

Ok thanks again for your help
Post Reply

Return to “Bet Angel - Automation”