Author Topic: True statement false  (Read 1422 times)

Tags:
  • All members
  • Posts: 823
True statement false
« on: 02 Jun 2014, 18:29 »
Hi,

I have had a couple of instances where bets have been placed when they shouldn't have been. It is to do with repeating bets.
Here are the logs in brief


17:16:40       Condition is: TRUE. valid for 1 selections: Yul Finegold.
17:16:40       Checking condition and Selection's Lay Matched is equal to 0
17:16:40   Checking market "Horse Racing / GB / 17:15 Chep 2nd Jun".
17:16:38   Remembering a set of 1 selections under the name of lastfav_114293218.
17:16:38   Going to LAY on 1 selections:

      Yul Finegold, $ 5.00 at 1.90;

Surely the log should show a "False" statement, as the bet was immediately matched
However there is only a 2 second delay between bet being matched and next log statement, could that be the reason?
In test mode this never happened once and went live today with only $5 bets and it has happened twice.
The execute is set at 'no more often than 0.1 sec' will changing this to say 1.0 help?
Thanks for any forthcoming assistance
R
My grandma taught me not to run downstairs and never back odds on.

  • √Člite
  • Posts: 3698
  • Gender: Male
*
Re: True statement false
« Reply #1 on: 03 Jun 2014, 13:14 »
hi
in the settings/betting options.
what do you have for the updating list of bets set at, defaut is 3 seconds, so 2 seconds the bet would not be updated.
for your requirement you need to tick simultaneously with refreshing the market


mcbee
Please read the following  disclaimer with regards to the information you may request and obtain on our forum. This specifically concerns trigger files and various instructions as to how to implement a strategy.

  • All members
  • Posts: 823
Re: True statement false
« Reply #2 on: 03 Jun 2014, 14:48 »
hi mcbee,
I learn something new every day, thanks for the tip
I will test it out
cheers
R

My grandma taught me not to run downstairs and never back odds on.

 

Please note, BetFair is seems to be currently OFFLINE