{deleted from 'automation' - reposted here as it's more of a support question}
Can anyone help please - I was hoping that the 'delay between resubmitting bets' and the logfile, will help me track down a problem I have with double trades in Guardian/Excel.
The default in 'behaviour' is 'wait 3 seconds' (although only for 'saved' bets - so I'm not sure if this applies to Guardian) and to save the log file on exit.
Unfortunately, neither seem to have any affect on Guardian - no log file and it still quite happily makes double bets (about 1 in 20 trades).
Also, the 'responsiveness' counter only seems to work for BA, not when making trades in Guardian.
Are there any plans to bring this level of diags and protection to Guardian, in the near future?
Thanks
Ian
BetAngel logfile and delay between resubmitting bets
Automation makes too many double bets to be trusted.
Support will tell you it's due to Guardian taking too long to refresh if you have lots of markets. Which to my mind removes one of automations supposed advantages.
I've given up on automation because of this.
Support will tell you it's due to Guardian taking too long to refresh if you have lots of markets. Which to my mind removes one of automations supposed advantages.
I've given up on automation because of this.
The saved bets feature is legacy and has been superseded by the Betfair 'Keep' or 'Take SP' bet persistence options.
The saved bets tab has been kept as there are some scenarios where some users find it useful.
The saved bets settings if active will work on unmatched bets submitted by Guardian automation or via Excel.
The double bet issue is likely to be something else. How many markets do you have in Guardian? Remember Guardian cycles through multiple markets and updates according to the refresh setting. Multiple markets cannot be updated real time due to the Betfair data restrictions.
I would increase the delay between bets and make this longer than your total Guardian cycle.
The saved bets tab has been kept as there are some scenarios where some users find it useful.
The saved bets settings if active will work on unmatched bets submitted by Guardian automation or via Excel.
The double bet issue is likely to be something else. How many markets do you have in Guardian? Remember Guardian cycles through multiple markets and updates according to the refresh setting. Multiple markets cannot be updated real time due to the Betfair data restrictions.
I would increase the delay between bets and make this longer than your total Guardian cycle.
6thSense wrote:The saved bets feature is legacy and has been superseded by the Betfair 'Keep' or 'Take SP' bet persistence options.
Ah, thanks for the explanation. Now I understand!
The double bet issue is likely to be something else. How many markets do you have in Guardian?
At first, I thought it was the PC performance, as the PC is quite busy at times, but another 8GB RAM sorted that out, so at the moment, I'm thinking that it might be network/API response latency. I normally have 30-50 markets open, restricting refresh to about 4 hours down to start time. That means it's updating 15-30 markets at any one time with a delay between individual work sheet refreshes of 5-10 seconds. I've reduced the data download (I don't care about full market depth, just the 3 key Bet/Lay figures).
I might have to invest in a virtual server with a good network connection, but as my systems earnt a grand total of 89p last week, maybe not.
Thanks for the help
Ian
Rinoa wrote:Automation makes too many double bets to be trusted.
Support will tell you it's due to Guardian taking too long to refresh if you have lots of markets. Which to my mind removes one of automations supposed advantages.
I've given up on automation because of this.
I agree entirely - I really don't see why Guardian can't be made a bit more reliable (well apart from developer time/cost!).
I'm thinking about moving over to the API, but that's quite a lot of work, although ultimately, it should be more reliable.
Ian