Performance Issue again

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Zhong
    Junior Member
    • May 2009
    • 14

    #1

    Performance Issue again

    This afternoon I encountered the performance issue in the horse racing market. For example I placed a 2 euro bet, it won't show in the open bet tab. Without knowing if the bet is successful, I would place another 2 euro bet. After 1 or 2 minutes, the 4 euro total bets are shown in the open bet tab. Basically I placed 2 euro more than I expected by encountering this performance issue.

    I believe everyone else also had this issue, because I had to wait 40 minutes to get the live help from the customer service.

    The customer service told me that it was true that the there was a performance issue. And Betfair is fixing that. And he assured me that "the bet is safe".

    I felt very disappointed because:
    1. There's no public page mentioning that there's a performance issue. People without knowing the issue (like me) will trust the exchange and place bets like normal, and face the operational risk without knowing what happens
    2. There's no public page mentioning when the issue is solved. Does Betfair expect us to contact the customer service again to make sure that the issue is solved? Isn't that too inefficient? Or is the best strategy is just to stop betting for the whole day to eliminate the uncertainty?
    3. When I checked the Betfair twitter account, I only see useless sports ads. Why not using the twitter account to broadcast the exchange status?
  • betdynamics
    Junior Member
    • Sep 2010
    • 534

    #2
    Site issues tend to get communicated through the @BetfairHelpdesk twitter account rather than the @Betfair account.

    They announced a problem with the Exchange at 14:34 this afternoon - although they rarely tell you what the actual issue is.

    Comment

    • Zhong
      Junior Member
      • May 2009
      • 14

      #3
      Originally posted by betdynamics View Post
      Site issues tend to get communicated through the @BetfairHelpdesk twitter account rather than the @Betfair account.

      They announced a problem with the Exchange at 14:34 this afternoon - although they rarely tell you what the actual issue is.
      Oh that's quite help info, thanks a lot for this!

      Comment

      • robne2000
        Junior Member
        • May 2013
        • 19

        #4
        Does anyone have a good way to code around this?

        During these errors my calls hits the timeout and therefore I have no way to know if the bet did place, or failed at betfair. Without the betid it's very hard to do anything about this.

        Comment

        • Ipposnif
          Member
          • Mar 2014
          • 36

          #5
          If you didn't get a response after a bet place, you can check its status with "listCurrentOrders" api. If also this api goes in timeout stop betting

          Comment

          • robne2000
            Junior Member
            • May 2013
            • 19

            #6
            I guess that's the only option. It's just not that easy when you might have a couple of hundred bets open, and new ones being created all the time.

            It'd be good if BF could specify a maximum time they'll take before responding, otherwise it'll cancel, and I can set my timeout accordingly.

            It appears their website does this - when I was placing bets manually today, I got a lot of messages stating that a bet hadn't placed due to a problem, usually after waiting 20 secs or so.

            Comment

            • OliasOfSunhillow
              Junior Member
              • Feb 2013
              • 57

              #7
              I found the new API-NG very flakey today. It was returning errors all over the place whilst normally it has functioned perfectly

              Comment

              • bnl
                Junior Member
                • Nov 2012
                • 108

                #8
                So did I. asking for prices was fine , and then asking again 5 sec later and no reply.
                very instable, all day. Bad.
                /Björn

                Comment

                • OliasOfSunhillow
                  Junior Member
                  • Feb 2013
                  • 57

                  #9
                  Good to hear someone else was experiencing problems. On the pus side it highlighted lots of areas where I need to trap exceptions in order to stop my program crashing. I have to say the old API is far more robust at the moment than API-NG

                  Comment

                  Working...
                  X