nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

MYOB API Running Slow Today

lloydd

Is anyone else experiencing this? Is it related to the 2FA change that went out overnight?

Find more posts tagged with

API outage

Accepted answers

All comments

Steve_PP

Ah Doc, we meet again. I would be great if MYOB provided an idempotency key feature for transactional inserts. Out of interest I find an average 1.5% failure rate, whereby 50% of time an invoice is 'silently' inserted, 50% not. To get around it, I track first send time and confirmation time. If i come around again in the processing queue to find an invoice to be inserted already has a first send time (but no confirmation time,) I search for the invoice in MYOB by my unique key stored in the PO number field. If found, I link to the invoice, if not found I try to reinsert. Seems to work well. I know the PO number won't be able to be commandered like this for everyone but another field might work.

Princess_R

Hi Bonso,

We understand that not having timely updates on our status page can be frustrating and lead to unnecessary investigations on your end.

We do share information and updates through our status hub page, which is our main channel for communicating such issues to both our internal team members and customers. You can subscribe to receive notifications by clicking the subscribe button on the status hub page to stay updated on any MYOB incidents.

Cheers,

MYOB

eJulia

If not using invoice numbers, which is optional, we check for duplicate invoices by comparing customer and sale data including customers number if supplied, JournalMemo if supplied, ShipTo Address if supplied and CurrencyCode if supplied. TransPost will not import a sale if it matches exactly on all the criteria. A similar test is applied to other transaction types. In the latest version the same test is reapplied, after a pause, when retrying.

The problem is working out just how long the pause has to be for this to be reliable. Today it seesm to have needed to be rather long.

The_Doc

Yep - really annoying - something that takes 11 mins - downloading of BackOrder invoices - took 46 mins - yes there are error loops to catch but I have had to broaden these in the last month trying to resolve appalling download times for BOrder invoices - grr .....

However, the reason I posted was a very annoying thing that I am not sure how to fix - if I post an invoice or a BackOrder - something that 'does occur' but today it has happened too many times - [ and yes I know if you turn on - 'warn if duplicate invoice numbers' - this will error your post so I turn it off ] - but when MYOB has another one of its 'Gateway timeouts' - an invoice can actually get through and be posted successfully but we still get a 'gateway error' - so my code says - 'ok try again to post' and you get a double up.

Apart from turning on 'duplicate invoice number warning' - anyone know a way to PREVENTING'

I am doing a mind exercise at the moment trying to consider so coding to check this??

The Doc

kjm

same. It appears to be up now. I undertsnd down time is part of online systems but I do wish MYOB would be a little faster in acknowledging there is a problem. My users are coming to me saying there is a problem. As I can not find anything on MYOB status.myob.com to indicate that there is aproblem I go ahead and start an investigation. I end up wasting time, energy and effort when I strongly suspect it is a MYOB outage but I have nothing to send to my users to confirm this.

Like I said, outages are aprt of online life. Everyone understands that and accepts it. If you could be a little more proactive and let us know that "you know there is an issue and it is being looked into" then I can send that to my users and everyone settles down. You might also find that you would receive less abuse.

Can you give any reason why this should not a SOP? @Princess_R

PhilWherrett

It does appear to have improved for us now - no errors in the last hour - from about 2:30pm AEST

Princess_R

Hi everyone,

Earlier today, we had a login disruption incident that has since been resolved by our dedicated team. To ensure optimal performance, please clear your AccountRight cache or your browser cache.

If you are still experiencing timeouts, please reach out to our support team directly. This will help us collect information on how many users are affected and provide further assistance. Sorry for the inconvenience caused, and thank you for your patience and understanding.

Cheers,

Princess

Hamishjam

Still having constant communication issues (Gateway Timeouts) - MYOB where are you?

mkaaaaaay

seems to be working now...

Unknown8580

Constant gateway timeouts since this morning.

ShikharITCC

Timeouts, not working but on status Page it's showing all resolved and UP..

kjm

timeouts, nothing working. Whats going on MYOB? some acknowledgement/information would be good

mkaaaaaay

An absolute joke. Timeouts, and errors in data pushes.

Hamishjam

We're also experiencing significant issues with this right now. Urgent action required.

Steve_PP

Yes. Absolute rubbish performance. Constant Gateway timeouts. It has taken 3 hours to insert 50 invoices

PhilWherrett

Yes - experiencing a lot of communication errors with (504) Gateway Timeout exceptions