Every execution made in Nexus, regardless of the Connector, will create a Request Message record. Here you will find all of the details of the transaction, including the overall status, related record id (if available), a copy of the API Response file, and a DML Results file for each Salesforce object being updated. Depending on the setup and complexity of the API, there may also be additional information included which will be included in the Connector specific instructions. For now, we will focus on the core information that is most common.
Choose the 'Request Messages' tab from the app to view the list.
The record is created once the Nexus process is initiated. This can be from executing an Outbound event, or in the case of a Webhook, it gets created when the Inbound message is received by the Nexus servers.
The Status will indicate the progress of the callout:
Sent - An Outbound Event has been triggered from Nexus.
In Progress - The Nexus servers have received the request and are processing.
Long Running Process - An 'asynchronous' connection is waiting for the 3rd party system.
Complete - The process has finished and appears to be successful.
Error - Something went wrong. The 'Message Detail' will have more information.
Click into a record to view more information.
The 'Details' panel contains the following basic information about the callout:
Related Record Id - The Record Id of the triggering record. This field is not populated when executed from the List Builder or and Inbound Only event.
Nexus Core Request Id - The unique Id from the Nexus servers. This value would need to be provided in a Troubleshooting Support Case with IOLITE to locate the backend system logs.
Inbound/Outbound Data Event - Lookup fields to the Event Mappings.
API Function Name - Friendly name of the function for easier identification.
Async Callback Function Name - Only populated on asynchronous functions (Long Running Process) that identifies the separate callback API Function Name.
Connector Id - Id of the connector making the callout. Can be useful in debugging issues.
Status - See above explanation.
Message Detail - More verbose description. Could contain success message, or details on a particular error that happened.
In addition to the main Details block, you will find related lists for 'Request Message Details', 'Files' and 'History'. RMD's are used by certain, more complex APIs that have multiple related items that take place during a callout. Use of this object will be outlined (if necessary) at the Connector Instruction level.
'Files' for most connectors will contain the raw Response body from the API if one is present. In the event of an unsuccessful transaction resulting in an 'Error' status, the Message Detail field will direct you to this file to get even more information about what caused the error (i.e. required information missing, or unsuccessful authorization). For successful transactions, this will simply be a copy of the response body that was returned. These will most likely be text files in JSON format, but could also be another format based on what is returned by the API. Completed transactions that have Inbound Events that are mapped will also usually have a 'Results' file for each Data Event Object mapping and the DML results. These CSV files are similar to the Success/Error files you would see using the Salesforce Data Loader and will identify if the record was updated or, if not, what caused the failure.