Every transaction event resolves to one of the following statuses. These statuses describe how the nChannel platform will behave as a reaction to the event. They are also criteria by which you can create email alerts.
Transaction events resolve to "suspended" when the action they intended to complete (i.e. inserting an order) has failed to complete successfully and is not likely to until a person intervenes. Effectively an error has occurred that is unrecoverable unless someone does something.
Suspended events can occur for the following reasons (not an exhaustive list):
- Inadequate or incorrectly structured data that was not validated in an earlier step of the data flow
- Response from a merchant-customized web service that nChannel's code did not expect and cannot react to
- Failures that have completed the "retry" algorithm without succeeding (see below)
- Authentication issues
- Insufficient or incorrect channel transaction configuration
- Failures on the host machine or OS (if using an installed SyncManager)
Transaction events resolve to "failure" when the action they intended to complete has failed, but for a reason that is expected to be recoverable in short order. When an event is marked as "failure", it will trigger nChannel's retry algorithm to keep attempting the same event until it succeeds.
The goal for "failed" events is to not involve a human for intervention until the system determines it's unlikely that the issue will resolve itself after a short time.
Failed events can occur for the following reasons (not an exhaustive list):
- Temporary API or system outages
- Unspecific 500 responses from an API (it's assumed that this is probably a temporary issue within the endpoint)
- API call limit throttling responses and high traffic/volume warnings
Transaction events resolve to "success" when they have successfully completed the intended action, and they have received confirmation of success from the endpoint system. These events do not require an human response or reaction, but it may be desired to send an email notification of successful events for operational purposes (e.g. notify of every new order entering an ERP).
Informational & Verbose
Transaction events resolve to "informational" or "verbose" when a channel is set up during the testing phase of an nChannel implementation to display more information than is normally required. nChannel technicians use this detail understand details of what's happening in a channel transaction. The typical user does not need to read or respond to these events and will typically not even see them.