Digital Assistant and Mobile

Get Involved. Join the Conversation.


    Where do I find more info on the error logs?
    Topic posted July 3, 2018 by Asser Green Ribbon: 100+ Points, last edited July 12, 2018 by Arijit ChakrabortyBronze Trophy: 5,000+ Points, tagged API, Bots, OMCE, Tip 
    221 Views, 2 Comments
    Where do I find more info on the error logs?

    I have tried to make a backend/API on OMCe and put these custom components there, following som tutorials.
    Apparently I have some errors somewhere in the code according to the error message.
    However, I cannot find where the error is. I've looked on the suggested sections but the message is the same.
    For example, I see "The API invocation ended. We couldn't start a custom code container because of an uncaught exception. This typically happens because there's an error in the custom API implementation. To find the error, go to the Logs tab on the mobile backend's Diagnostics page. The Message Detail dialog box for the log message displays the module and line number where the error occurs. Fix the error and try again.", but when I go to Backend -> Diagnostics -> Logs tab, instead of a line number I find this exact message (see attachment).

    Is there any way I could get more details about the error? As it is very hard to fix it when I don't know where the error occurs.




    • Frank Nimphius


      agree that this could be more verbose.


      if this problem shows upon component registration then its mostly 

      - a missed import of the dependency (SDK required JOI). So you may have forgotten to call npm install on the folder with the package.json file

      - the registry does not contain the correct component reference

      - you have a malformed JavaScript in your implementation file

      Usually the diagnostic logs provide you good hints on what is missing except for when the crash is immediate, which usually leads to HTTP 500 and no message


      A better option to build this easier is to setup end-to-end debugging for a custom component. This involves the use of the OMCe tooling (available on OTN) as well as some hints on local debugging (available on Oracle TechExchange blog). As we do run a full session on this in an upcoming advanced training I have a todo-list item for myself to document debugging. 

    • Martin Jarvis

      Hi Asser,

      I agree with Frank. The Custom Code Test Tools are the way to go. You run your custom code in a nodejs container locally of your development machine, but the toolkit proxies all MCS SDK requests up to the server. You get full client side debugging before you deploy fully to the server.

      Custom Code Test Tools v18.1.1.0