Pages:
Actions
  • #16 by Maddox on 06 Nov 2009
  • Nothing in my log files about failures and yes Oxa that is correct
  • #17 by Oxa (WellDoneSoft) on 06 Nov 2009
  • Quote from: Maddox on 06 Nov 2009, 13:13
    Nothing in my log files about failures and yes Oxa that is correct
    So, just to be sure, you don't have anything in that folder?
  • #18 by Maddox on 06 Nov 2009
  • I do but not for today

    Last file "05_11_2009.txt"
    says
    18:47:58:   Unable to send request, 33 The connection with the server was terminated abnormally

    18:48:00:   Unable to send request, 33 The connection with the server was terminated abnormally

    Error while getting funds at BF:

    Nothing to do with the current problem.
  • #19 by betfair winner on 06 Nov 2009
  • Yes.....
     I too have checked these files, and there a number of entries for dates early in October, but there are no entries for the dates that i am refering to in my post earlier.
    the error messages in the early dates are as per Maddox above.
  • #20 by alfaman on 06 Nov 2009
  • Well I'v gort home today and looking back up the events in My Martets there are many that have been settled but, 22 Greyhound events and 7 Horse racing events have bets placed and still showing - ie not settled so not in the statement.

    I think the GH are all from Oxfd, Monm, Swin and Hove although some Oxfd events have been settled and the unsettled horse events are only from Hexham.

    No failure log created for today.
  • #21 by alfaman on 07 Nov 2009
  • And surely this can't happen ????????????   :o

    Is it me, or my MF pro at fault ?
  • #22 by betfair winner on 28 Nov 2009
  • It happens to me every single day now!  ::)
    Bets are fired in and results appear on the statement as usual, but then suddenly the results from the action log from rss betfair saying that the bets have been settles just stop!
    For a whole hour yesterday around 40 bets were fired in on greyhounds and horses with none settled on the statement.
    I now re boot MF pro and everything then works OK but having to monitor the whole process is simply not possible sometimes.
    Did you make any progress on this Oxa ?
  • #23 by alfaman on 28 Nov 2009
  • Betfair Winner,

    Mine too,  as well as sometimes it is intermittant.  Yesterday when I came home it was still settling horse racing events at 6pm but since about 2pm most dog races had not been settled.  I had to manually settle them by looking at RSS and selecting the winner. Most annoying.  Once I had done this I stopped and retarted just in case.

    Do you find it correctly settles past events after a re-start ?

    I can only deduce that either this only affects a few of us, or no one else notices, or they do have it but don't mention it here.
  • #24 by betfair winner on 28 Nov 2009
  • Hi Alfaman
    Sadly restarted does nothing to get the statement updated with missing matched bets. Restarting will only correct the problem from the time of the re start.

    I find it slightly unusual also that only a handful of people have mentioned this problem as not only is it impossible to test a trigger for consistency, reliability let alone profitability it means you have to spend hours trawling through the bets and entering each one manually. Maybe we are just spoilt but this robot is supposed to do this for us!

    I have written to support regarding this issue in the hope that after all this time since bringing the problem to their attention someone may finally be getting to grips with the answer to the problem. :-\
    Lets hope so because the future looks bright if only we can get the result problem sorted…
    Hey ho …………………………
  • #25 by JS on 31 Aug 2011
  • Hi guys,

    Am curious to see if this is still an issue for anyone with the latest version?

    Recently I have been having issues with events not monitoring when my monitoring options are set for the markets to be monitored at 1 min before the event.

    The only way I can fix this is by manually starting the markets myself periodically, or rebooting MFPro completely, after a reboot the market monitoring resumes normally. This then stops working again after some time (I'm thinking it is linked to when more markets are added to 'my markets' but I'm not entirely sure why it stops). 

    This is inconvenient as I often have hundreds of idle markets in 'my markets' and each reboot takes about 20-30 mins.

    Any ideas? I'm all ears!

     
  • #26 by Tim (WellDoneSoft) on 31 Aug 2011
  • If you run and then stop market manually MF pro remembers this state and never runs market again. You would never be able to stop the market in other case.
  • #27 by mcbee on 31 Aug 2011
  • hi
    this will happen if you have set your request limit to low in the monitoring settings (the graph icon top right of the bot screen)
    also if you are monitoring lots of markets at the same time, it will happen because the bot will cease monitoring markets if any new markets to monitor takes the refresh limit over your settings.


    mcbee
  • #28 by JS on 31 Aug 2011
  • Thanks you for your prompt replies guys.

    I am only actively monitoring about 5 or so markets at one time (whilst they are in play), on a busy day perhaps about 10, MFPro & my PC seem to handle this fine so I don't think it will be the refresh settings.

    I think it is most likely because of the starting, stopping and then needing to restart the markets later that this is happening.

    Can I ask as my tactic involves adding markets early, placing some orders to keep for when the markets go inplay, then stopping the monitoring until a min before the start, I then want to resume monitoring automatically of each market for the triggers to fire in the closures at the appropriate moments.

    Is it actually possible for me to do this without needing to reboot MFPro in the middle? 

    Thanks again for replies.     :)


  • #29 by JS on 31 Aug 2011
  • If I were to use the 'stop refresh market' action trigger within my process after my initial orders have been placed, will the monitor markets kick in again later if set to 1 min before off? Or would it be the same effect as manually stopping the markets?


  • #30 by Tim (WellDoneSoft) on 31 Aug 2011
  • It's better not to stop the markets but set their refresh rate for say 60+ seconds after the first bets and then back to 1 second at 1 minute before the off.
Pages:
Actions