Company: Link Technologies
Case No: L12867. Project: 14.60: LinkSOFT Version 14.60 - April 2023
Logged By: Sanjay (Link Technologies) on 25 Mar 2023 12:44PM
Priority: High
Product: FMIS (Jiwa/Epicor/etc)
Group: Software Defect
Time Taken: 66.00 (Weight: 86.00)
Assigned To: Sanjay (Link Technologies)
Circulation: Sanjay
Resolve By: Friday, 31 March 2023 12:00 AM [394 days since logged date]
Status: Closed
Subject: MYOB API - Internal Error - An exception was thrown that was not handled correctly. If this situation persists please contact developers@myob.com for further assistance.
Summary:    

Error message:
{ "Errors": [ { "Name": "InternalError", "Message": "An exception was thrown that was not handled correctly. If this situation persists please contact developers@myob.com for further assistance.", "AdditionalDetails": null, "ErrorCode": 20, "Severity": "Error", "LearnMore": null } ], "Information": "Warning, error messages have not been finalised in this release and may change" } Integration: MYOBAccountRightV2.API Rule: GeneralLedgerMaster Flag: GLAccount.URL.GET

{ "Errors": [ { "Name": "InternalError", "Message": "An exception was thrown that was not handled correctly. If this situation persists please contact developers@myob.com for further assistance.", "AdditionalDetails": null, "ErrorCode": 20, "Severity": "Error", "LearnMore": null } ], "Information": "Warning, error messages have not been finalised in this release and may change" } Integration: MYOBAccountRightV2.API Rule: AccountsReceivableTransaction Flag: QuoteTimeBilling.URL.GET

{ "Errors": [ { "Name": "InternalError", "Message": "An exception was thrown that was not handled correctly. If this situation persists please contact developers@myob.com for further assistance.", "AdditionalDetails": null, "ErrorCode": 20, "Severity": "Error", "LearnMore": null } ], "Information": "Warning, error messages have not been finalised in this release and may change" } Integration: MYOBAccountRightV2.API Rule: AccountsPayableMaster Flag: ContactSupplier.URL.GET

Audit Notes:Edited by sanjay on 25/03/23 12:44. 
25 Mar 202311:56AM Comment 1 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 27-03-2023 05:54 PM Time Taken: 18.00

Seems like this error is intermittent and happens when all the MYOB APIs are enabled. It could be that the MYOB local Service is overwhelmed and raises an internal error.

I have been able to re-produce the issue by bombarding the MYOB API with multiple API calls all at once, however, when we throttle the API calls, the error does not happen.


25 Mar 202312:02PM Comment 2 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 27-03-2023 05:56 PM Time Taken: 26.00
PART A - Development work for this case has been completed.

1. The change will be available in version: 14.60

2. The following changes were made(Include Database object names, Program classes, and any other relevant information):

  1. Added a flag named: "General Settings.DelayBetweenAPICalls". Default Value 1000 Milliseconds. This will allow 1 call per second throttle for all API's under this integration.
  2. Added a flag "XXX.URL.GET.LastReadDateDelay". Default value 60 seconds. This is the amount of time (in seconds) to delay between API calls for a specific module. Recommend the following settings:
    1. For Masterfiles - set this to 600 seconds (10 minutes). If your Masterfile changes very frequently, use something like 120 seconds (2 minutes)
    2. For Transaction files, recommend this value to be 60 seconds.

3. Affected Areas:

  1. Integration API calls where there is a throttle limit

4. The issue was caused by:

  1. Throttle Limits on API from external systems

5. Other Relevant Notes
6. Next Step
(Review and System Test (Developer) -> UAT (Quality) -> Documentation): UAT


25 Mar 202301:37PM Comment 3 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 27-03-2023 06:44 PM Time Taken: 22.00 Notes: Edited by sanjay on 25/03/23 13:38. 
The following tests were performed:

Test Setup Instructions:
  1. Setup MYOB Accountright 2023.1
  2. Configure LinkSOFT MYOB API using the recommended settings in comment 2
Table 1 - Test Results
NoTest CaseExpected ResultPass/FailComments
1Enable all integrations and monitor the Error log
All integrations should start processing. Review Process Maintenance Log to see each API call
Pass

2Edit Tax Master
Changes should reflect in LinkSOFT after 2 minutes
Pass

3Edit AR and AP Master
Changes should reflect in LinkSOFT after 2 minutes
Pass

4Create an Invoice in MYOB
The invoice should import via AR Transactions
Pass

5Create an Invoice in LinkSOFT
The invoice should Post to GL
Pass

6
Review Error Logs after 2 hours
There should not be any errors in the Logs relating to MYOB
Pass

Environment Details

  1. OS version: Win11
  2. Application version: 14.60.0325
  3. Setup on:
    1. Server: LinkQA4
    2. Database: LinkSOFT
    3. LinkSOFT URL: HTTP://LinkQA4/LinkSOFT
  4. Login Details: Standard username and password for user "admin"

Next Step: Closure


If you have any queries regarding this support incident, please email admin@linktechnologies.com.au and include the Case No: L12867 in the subject line of all emails regarding this issue.

Document size: 13.6 KB
For call complaints, please contact the Managing Director of the company using this form