Inbound Action triggered by new email fails to create record for script runtime error

a) A new email arrived to the instance, however no new incident was created.  

The email record's log section shows that the Inbound action was fired but no record was created or updated:

Skipping 'Create Incident', did not create or update Incident.
Stop processing detected after executing script: Create Incident.

b) You browse the nodes log files at the time of the inbound action, and there is evidence that the inbound action script finish with an error:

*** WARNING ***Evaluator: org.mozilla.javascript.EcmaError: "mylookup" is not defined. 
Caused by error in sysevent_in_email_action.aff0ada71c540100db369016842fd3ab.script at line 25

Any supported release

You will get this type of error when somehow the script executed by the inbound action returns a runtime error.

In the particular case showed here the inbound action script was set to call a script includes, but the call did not include the API namespace causing a script execution failure and no incident was created or updated. 

Inside the inbound action code, there was a call to a script includes named 'mylookup' and method getData() which was not found at execution time since was not called including the namespace. 

This is how it was called:

 var myvalue = mylookup.getData(email.subject); 

This is how it should be called:

var myvalue = <API_namespace_here>.mylookup.getData(email.subject); 

If there are many different application scopes in the instance where this inbound action runs, the script namespace is required to uniquely identify the object being called.

Include the API Namespace in the script call in all inbound actions that calls script includes. The issue was resolved after include the API Namespace in the Script includes call.