We are connecting with RTC and creating WorkItem from Outsystems using POST Request which is working fine.
However when I create call the same REST API call 2nd time, it throws 409 Conflict error. Different structure instance is used for each POST request. Checked parameters, looks same.
Not sure what is causing this error. Anyone can helps us
Please enable Logging level to "Full" (Service Center -> Module -> Integrations -> Consumed REST APIs ) and compare both requests and see the data is indeed different in both cases. It might be possible that same data is pushed the second time.
Sure Siya, I will update the logging configuration and compare. However both requests have 11 parameters, only 4 parameter values will vary, rest of 7 parameter values are same. This is my requirement. I hope that 4 parameters makes difference. I will check it again with your important insights. thank you
Checked the parameters, identified incorrect parameter and it worked fine. Detailed log helped us to find the root cause. Thanks much for your support :)
Hi Manivannan,
A 409 is a functional error, not a technical one. It simply means that you sent the REST API data that it cannot process, due to a conflict (so not due to a malformatted message, or missing data, but e.g. because you ask it to create something that already exists).
It is not an OutSystems error, and not something that the community can directly help you with. Please carefully read the documentation of the REST API, and see what can cause a 409.
Siya's advise is a solid one, set the logging level to Full and check the logging. Often you will see that the REST API sends error information explaining what exactly you're doing wrong. For example, here's a recent 409 I got in our software when sending a duplicate contact:
As you can see, in the error message there's information on what we did wrong.
Hello Kilian Hekhuis,
Enabling full log really helped us to find the root cause. Unfortunately one of parameter(parameters here encrypted format) was incorrect, earlier default error message didn't shows the details. Now detailed error message is displaying the exact parameter mismatch.
Your inputs really helped to nail down the root cause. Thanks a lot for your quick support
Great to hear you got it solved Manivannan! Happy coding!