EncompassRest
EncompassRest copied to clipboard
EncompassRest
general "Conflict" error when trying to upate loan
I get this error a lot when trying to update a loan. Anyone know what this is, the message itself isn't terribly helpful.
EncompassRest.EncompassRestException: UpdateLoanAsync: {8b140660-9be4-4390-ab40-b886e2e6e2b9} - 409: Conflict - CorrelationId: 8c2a3fca-8665-4236-8352-3e527cc9114b
{"summary":"Conflict","details":"Loan processing failed"}
at EncompassRest.ApiObject.d__42`1.MoveNext() in C:\Users\tbrinkley\source\repos\EncompassRest\EncompassRest\src\EncompassRest\ApiObject.cs:line 146
A majority of the time this CONFLICT status code appears is when there's a Business Rule that conflicts with the information you provided the API.
Hmm. Interesting. Is there any way, using that correlation ID that is returned or something to get more information about what is being returned? I realized i was not locking the loan, so in theory someone else could've updated it while I was trying to as well. However I've since added the code to lock the loan exclusively first, but I still get that error. So I think I've eliminated the possibility of colliding with another user. So the business rules would seem the most likely now.
From looking at the EM developer doc, it looks like this is the error being returned by Ellie Mae? Not an error from EncompassRest i think, correct?
So i guess i'm wondering now if EM exposes, and ER wraps, any kind of call to pass the correlation id or maybe a "verbose" argument to the calls, to try to get more information about the conflict?
Correct; explanation isn’t overly helpful … 409 Conflict Returned when the requested service call conflicts with the current state of the object of the service.
But, it does make it sound like a business rule or other type of conditional logic is in place that whatever you are updating is potentially not an accurate update. Not sure depending on how you have it updating if you can isolate the loan itself and the individual field or values you are updating to validate.
From: Aaron [email protected] Sent: Monday, June 29, 2020 5:50 PM To: EncompassRest/EncompassRest [email protected] Cc: Subscribed [email protected] Subject: Re: [EncompassRest/EncompassRest] general "Conflict" error when trying to upate loan (#343)
Hmm. Interesting. Is there any way, using that correlation ID that is returned or something to get more information about what is being returned? I realized i was not locking the loan, so in theory someone else could've updated it while I was trying to as well. However I've since added the code to lock the loan exclusively first, but I still get that error. So I think I've eliminated the possibility of colliding with another user. So the business rules would seem the most likely now.
From looking at the EM developer doc, it looks like this is the error being returned by Ellie Mae? Not an error from EncompassRest i think, correct?
So i guess i'm wondering now if EM exposes, and ER wraps, any kind of call to pass the correlation id or maybe a "verbose" argument to the calls, to try to get more information about the conflict?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/EncompassRest/EncompassRest/issues/343#issuecomment-651387744, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGJV2U4TVYAA66LN6OUQMJ3RZEEANANCNFSM4OLKAERQ.
TVMA, Inc. trades as Teraverde Management Advisors | Intellectual Property provided by Teraverde Financial
Confidential Electronic Mail Notice: The information contained in this message is intended only for the persons to whom it is addressed and may contain privileged material. Copying, distributing, dissemination, reliance on, or other use of the information by persons other than the intended recipient(s) is prohibited. If you received this message in error, please notify the sender and delete the entire message from any computer.
Yes, let me parse the error message for you.
EncompassRest.EncompassRestException is the type of Exception that was thrown which is used for unsuccessful API calls.
UpdateLoanAsync is the method that was called that tried to make the API call and {8b140660-9be4-4390-ab40-b886e2e6e2b9} is the id of the resource you were trying to access which in this case is the loan id.
409: Conflict is the returned HttpStatusCode.
CorrelationId: 8c2a3fca-8665-4236-8352-3e527cc9114b is the id you would give Ellie Mae to inspect in a support case ticket. It is returned from the HTTP response header X-Correlation-ID.
and {"summary":"Conflict","details":"Loan processing failed"} is the response body from the API call.
Eh. So the correlation id is sort of useful, but would require an actual support call with EM? That sounds like trying to swim in jello. I guess really the only way to isolate it then would be to update/commit each field individually, and try to see which one is the one failing? Like rbpeterson2 said above.