Skip to main content
Skip table of contents

Interpreting integration logs

View integration logs to validate processing times, identify performance issues, and troubleshoot reported errors with external applications and processes.

A developer can configure logging of exceptions for an outbound service and logging of descriptions in NexJ Studio.

The following information is stored in the NJIntegrationLog table. The Serialized RequestSerialized Response, and Exception information for filtered log files is available on the Integration Log page in NexJ System Admin Console.

All errors are assigned the ERROR log level and are written to the Exception column in the NJIntegrationLog table.

User ID

The user sending or receiving the request. If no user is associated with the request, then the ID for the nexjsa is used.

Node ID

The ID of the node the request was sent or received on


The name of the channel associated with the request


The time an outbound request was sent or an inbound request was received


Duration of the request in milliseconds


The address the request was sent to

Serialized Request

A serialized text version of the request

Serialized Response

A serialized text version of the response

Severity Code

The logging level associated with a log entry, where E is Error, W is Warn, I is Info, D is Debug, and U is Dump


The error code or exception of the request or response, if any occurred. Includes the relevant stack trace.


Optional notes associated with the log entry. By default, the description returns no logging information.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.