Forum Discussion

Bdenford's avatar
Bdenford
Contributing User
7 years ago

MYOB 2019.2 API Random 500 Internal Errors

Hi All,

 

I have an application that very recently has begun getting random 500 Internal errors when querying various endpoints on the MYOB Account Right API. At times it is working fine and at other times it will throw the error constantly. Wait 15 mins and the API is working OK again, 10 mins later 500 errors.

 

Is there any issues known with MYOB 2019.2? 

Could an 500 error be an API limit issue? 

 

We have experienced this on numerous company files across numerous different MYOB accounts on different internet connections. Only common theme is Myob 2019.2.

7 Replies

Replies have been turned off for this discussion
  • MickDevine's avatar
    MickDevine
    Valued Cover User
    7 years ago

    You're not the only one. We reported this last week and apparently the engineering team are looking at it.

     

    cheers, Mick

     

     

  • HelenB's avatar
    HelenB
    Former Staff
    7 years ago

    Hi Bdenford,

     

    Thanks for reaching out. So the API Support Team can take a closer look, please reach out to them directly at developers@myob.com with a full HTTP Trace (including request and response headers, URI and message body/JSON).

     

    Thanks

     

     

  • We are also experiencing this problem. Unfortunately because of its apparent sporadic nature, it is difficult to get a full HTTP trace as it's hard to replicate in a one-off isolated API call. We will continue to try nonetheless but we do have a lot of clients that appear to be impacted in the meantime.

  • Bdenford's avatar
    Bdenford
    Contributing User
    7 years ago

    I should be able to get one.... Every 4-5 tries it happens to us.


  • Bdenford wrote:

    I should be able to get one.... Every 4-5 tries it happens to us.


    Thanks Bdenford! - we'll try to do a few requests close together and see if that brings it about

  • Bdenford's avatar
    Bdenford
    Contributing User
    6 years ago
    Well, since late last week the error is gone.... For now.

    Anyone else still experiencing issues?