question

Graham Sutcliffe avatar image
Graham Sutcliffe asked

500 status error with Mortgage Application Import

Received the following error response with traceId and ff-trace-id. We had an issue like this also a couple days previous, but that was because of sequenceNumbers not in order. This one appears fine with the sequenceNumbers.

{ "title": "An error occurred, please try again later.", "status": 500, "traceId": "0HMM2S4MT992E:0000051E"}


ff-trace-id: ef3cfd13b3964ad19ba7fdf55822839b

API - Lending
1 comment
10 |600
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

sanjay.patel1 avatar image sanjay.patel1 ♦♦ commented ·

Hi Graham, sorry for not replying earlier. We are looking into it and will get back to you as soon as we have an answer

0 Likes 0 ·

1 Answer

Graham Sutcliffe avatar image
Graham Sutcliffe answered

Any update?

3 comments
10 |600
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

sanjay.patel1 avatar image sanjay.patel1 ♦♦ commented ·

Hi Graham, sorry for not replying earlier. We are looking into it and will get back to you as soon as we have an answer

1 Like 1 ·
sanjay.patel1 avatar image sanjay.patel1 ♦♦ sanjay.patel1 ♦♦ commented ·

Hi Graham, we had escalated this issue to Mortgagebot team and have heard back from them

They suggested you to review the Mismo 3.4 XML payload as the Party_1 just includes a TaxPayerIdentifier while Party_2 includes more details on the borrower including a duplicate TaxPayerIdentifier

Also, it looks like something on that loan isn't correct

1 Like 1 ·
Graham Sutcliffe avatar image Graham Sutcliffe sanjay.patel1 ♦♦ commented ·
Thank you. We have identified a step in our workflow where the TaxPayerIdentifier could be duplicated.
0 Likes 0 ·