Hi,
We've noticed a massive spike in an "Object reference not set to an instance of an object " error when a call is made via the HttpsConsumer integration. From the 13th of April, it went from rarely occurring, to around 50-70 occurrences a day of this error. An example of the error messages we get:
All the errors seem to occur when we make the ConsumeRest_Get_SessionMaintenance call.
After investigating, the values are being assigned to the input parameters, and there has been no code change from our end recently.
Please do you have an idea of what could be the cause of this, or if there is a better way for me to investigate the issue.
Thanks for your help, and please let me know if you need any more information.
Hi @Emmanuel Sobamowo
This error might be due to empty/null response parameter getting assigned at your end:
- Try to add debug to trace the error point
- This might be at the request or response; were any one attribute is not getting initialized.
Good Luck
a while ago outsystems platform was upgraded and there was a change made to the consumed apis. before the said upgrade the request model did not contain request parts model and after the upgrade request parts was introduced. see attached pictures of OLD vs NEW:because the change for whatever reason the request model in the apis created AFTER the upgrade throws this error of object reference not set to an instance of an object in the on before request. IF you have a consumed api that was created BEFORE the upgrade you can copy that and reuse it in all apps and modules that you need and you will not encounter any issues. HOWEVER, even thou the object error the actual call does not fail necessarily you just can not modify it like to manipulate headers or parameters.PS: outsystems team might want to look into this as this is easily reproduced.@OP sorry this will not fix your issue but it will give you an insight into the error