MYOB API Running Slow Today
Is anyone else experiencing this? Is it related to the 2FA change that went out overnight?
Forum Discussion
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.
Hi Steve_PP
Thanks for the input - food for thought - can't say I have a figure for fail but it 'seems' that it is easier to assume it hasn't been inserted and go around again as my invoices are quite complex and I don't store a backup format of the invoice to be able to run again.
Not sure how I am going to handle it, but it is good sleep material or running fodder - since posting my invoice numbers are unique and should not be duplicated - but having said that I can download item invoices, but this just adds another big payload to just check whether invoice numbers are duplicated.
At present downloading Sales Orders (back orders) is a lumpy, problematic and prone to a lot of timeouts and is under investigation by MYOB API - so doing this with actual invoices to just get their numbers gives me chills - but I may not have any alternative - let me look at your suggestion and see if it will work.
Thanks
