getAccountStatement() - UNEXPECTED ERROR

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • footlong
    Junior Member
    • Nov 2016
    • 8

    #1

    getAccountStatement() - UNEXPECTED ERROR

    Following on from today's issues settling bets (which may be related?), I am unable to complete looping over all available account statements. I am getting this continually, after obtain 600 records, and trying for the next 100:

    Code:
    Error: {'code': -32099,
    'message': 'AANGX-0003',
    'data': {'exceptionname': 'AccountAPINGException',
    'AccountAPINGException': {'requestUUID': 'ie1-aanbf05b-prd-02080927-0015324ace',
    'errorCode': 'UNEXPECTED_ERROR',
    'errorDetails': ''}}}
    Any idea what's going on, or if it will be fixed?

    Thank you.
  • andychat
    Junior Member
    • Aug 2019
    • 1

    #2
    i'm getting the same error - after 600 records - can this be looked at pls. Thanks.

    Comment

    • MrMagoo
      Junior Member
      • Oct 2018
      • 5

      #3
      Me too. It started since about 16:20 yesterday and since then it's broken my record keeping. I am receiving the exact same response as footlong - in my case from record 300 onwards.

      Comment

      • Vadimaster1
        Junior Member
        • Jun 2013
        • 3

        #4
        Same problem. Started yesterday, I confirm.

        Comment

        • BetfairDeveloperProgram
          Administrator
          • Oct 2008
          • 679

          #5
          Morning All,

          We are currently investigating this issue and will confirm as soon as we have an update.

          Thanks

          Neil

          Comment

          • BetfairDeveloperProgram
            Administrator
            • Oct 2008
            • 679

            #6
            Hi All,

            This issue has now been fixed, apologies for the inconvenience caused by this

            Neil

            Comment

            • footlong
              Junior Member
              • Nov 2016
              • 8

              #7
              Thanks Neil, confirmed that it's working again.

              Comment

              • MrMagoo
                Junior Member
                • Oct 2018
                • 5

                #8
                It's mostly working for me, I'm still seeing intermittent UNEXPECTED_ERROR responses though. Retrying the same requests does get them to work in the end though.

                Comment

                • footlong
                  Junior Member
                  • Nov 2016
                  • 8

                  #9
                  Originally posted by MrMagoo View Post
                  It's mostly working for me, I'm still seeing intermittent UNEXPECTED_ERROR responses though. Retrying the same requests does get them to work in the end though.
                  Yes, agreed. I have had intermittent UNEXPECTED_ERROR responses for a while, but generally retry a couple of times and hey presto.

                  Comment

                  • footlong
                    Junior Member
                    • Nov 2016
                    • 8

                    #10
                    Hi Neil

                    This error appears to have resurfaced. Have tried ~10 times, always fails from record 1000 with error as per original post.

                    Thanks

                    Comment

                    • footlong
                      Junior Member
                      • Nov 2016
                      • 8

                      #11
                      The problem seems to have resolved itself this morning.

                      Comment

                      • NatHunter
                        Junior Member
                        • May 2012
                        • 8

                        #12
                        Hi Folks.
                        I have started getting the same 'AANGX-0003' error as described above.

                        I've not seen this before - my VB.NET code for retrieving account statement data has not changed for a long time.

                        is this an error on the system side or is it my code?!

                        Thanks for any help on this

                        Comment

                        • footlong
                          Junior Member
                          • Nov 2016
                          • 8

                          #13
                          Yep, AANGX-0003 is back this evening.

                          Comment

                          • NatHunter
                            Junior Member
                            • May 2012
                            • 8

                            #14
                            It's working OK this morning - seems to be intermittent, then. Will keep an eye on it.

                            Comment

                            • Martins
                              Junior Member
                              • Nov 2020
                              • 1

                              #15
                              I have the same problem. Can anyone help me?

                              Comment

                              Working...
                              X