Skip to end of metadata
Go to start of metadata


QUESTION:How do I check for failed notifications (in the Notifications Event Queue) & what do I if notification/s have failed?

ANSWER:

The Notifications Events Queue is the repository for all Notification Events that have been issued & allows you to enquire upon any events to check when they occurred and whether or not the notification E-mail, SMS or User Notification messages were sent or there were errors. This is where you find bugs or issues with failed Event Notifications.

System Administrators receive email notifications of any Event Notification failures. Currently (as at ) neither DeTrack or GetSwift provide Frameworks notifications of failed event notifications.


 Further information about GetSwift failures

If there is a failure for GetSwift:

1. An email is sent to the nominated email address in the GetSwift configuration:

Example email:

 Example of a successful GetSwift log file event:
Log File OutputDescription
Event registeredSelf explanatory
2018-06-20 10:05:01: GetSwift Order: Compress Command: zip -j /prostix/live/getswift/send/ORD_00085462_20180620100501.ZIP /prostix/live/getswift/send/ORD_00085462_20180620100501.XML
2018-06-20 10:05:01: GetSwift Order: Result:   adding: ORD_00085462_20180620100501.XML (deflated 69%)
2018-06-20 10:05:01: 
The xml file is zipped.

2018-06-20 10:05:01: GetSwift Order: FTP command /prostix/bat/M10DMSISend.sh rxpsterland /prostix/live/getswift/send/ ORD_00085462_20180620100501.ZIP root ***** 7 
2018-06-20 10:05:03: GetSwift Order: Result: Version 180329
2018-06-20 10:05:03: find /prostix/live/getswift/send/archive/ -mindepth 1 -mtime +7 -delete
2018-06-20 10:05:03: function: upload file...
2018-06-20 10:05:03: 
2018-06-20 10:05:03:    ======================================================
2018-06-20 10:05:03:    Wed Jun 20 10:05:01 AEST 2018 ... Uploading file
2018-06-20 10:05:03:    ======================================================
2018-06-20 10:05:03:    SITE=rxpsterland
2018-06-20 10:05:03:    SEND_DIRECTORY=/prostix/live/getswift/send/
2018-06-20 10:05:03:    SEND_FILE=ORD_00085462_20180620100501.ZIP
2018-06-20 10:05:03:    USER=root
2018-06-20 10:05:03:    SSHPASS=*****
2018-06-20 10:05:03:    DESTINATION_DIRECTORY=/root/INCOMING
2018-06-20 10:05:03: Uploading file... *****
2018-06-20 10:05:03: spawn sftp -oStrictHostKeyChecking=no root@rxpsterland
2018-06-20 10:05:03: root@rxpsterland's password: 
2018-06-20 10:05:03: Connected to rxpsterland.
2018-06-20 10:05:03: sftp> cd /root/INCOMING
2018-06-20 10:05:03: sftp> put ORD_00085462_20180620100501.ZIP
2018-06-20 10:05:03: Uploading ORD_00085462_20180620100501.ZIP to /root/INCOMING/ORD_00085462_20180620100501.ZIP
2018-06-20 10:05:03: 
2018-06-20 10:05:03: sftp> exit
2018-06-20 10:05:03: RC 10
2018-06-20 10:05:03: spawn sftp -oStrictHostKeyChecking=no root@rxpsterland
2018-06-20 10:05:03: root@rxpsterland's password: 
2018-06-20 10:05:03: Connected to rxpsterland.
2018-06-20 10:05:03: sftp> cd /root/INCOMING
2018-06-20 10:05:03: sftp> put ORD_00085462_20180620100501.OK
2018-06-20 10:05:03: Uploading ORD_00085462_20180620100501.OK to /root/INCOMING/ORD_00085462_20180620100501.OK
2018-06-20 10:05:03: 
2018-06-20 10:05:03: sftp> RC 10
2018-06-20 10:05:03: 

(info) A Pass/Fail is indicated by the message below

2018-06-20 10:05:03: GetSwift Order: XML write was successful
2018-06-20 10:05:03: GetSwift Order: Exported successfully

(info) Any unsent XML's will then be processed as per the message below

2018-06-20 10:05:03: GetSwift: Checking for unsent data...
2018-06-20 10:05:03: GetSwift: No unsent files found

(info) Footer data below to indicate that the notification got to the end of the routine

2018-06-20 10:05:03: Completed GetSwift Exports
2018-06-20 10:05:03: Processed  

The FTP script is executed.

(warning) On failure, carefully read this output to identify why the failure occurred. (warning)

A value of RC10 at the end of this section indicates the GetSwift Notification was successful.

 Example of a failed GetSwift log file event:
Log File OutputDescription
Event registeredSelf explanatory
2018-06-20 10:07:43: GetSwift Order: Compress Command: zip -j /prostix/live/getswift/send/ORD_00085462_20180620100743.ZIP /prostix/live/getswift/send/ORD_00085462_20180620100743.XML
2018-06-20 10:07:43: GetSwift Order: Result: ?
The xml file is zipped.

2018-06-20 10:07:43: GetSwift Order: The FTP password is blank
2018-06-20 10:07:43: GetSwift Order: FAILURE on GetSwift Order Export
2018-06-20 10:07:43: GetSwift: The FTP password is blank/
2018-06-20 10:07:43: Completed GetSwift Exports
2018-06-20 10:07:50: Error creating GetSwift export files for Action:Track-GetSwift/Seq:1
2018-06-20 10:07:50: Processed

The FTP script is executed & fails.

In this example, you can see the failure is due to a missing FTP password.

(warning) On failure, carefully read this output to identify why the failure occurred. (warning)


(info) As at  , for DeTrack, there is currently no indication in the log of failure, except that the notification is marked as an error, which is written in plain english detailing the error in the JSON data output. This will be changed in the future.

To search for failed Event Notifications & to reprocess them, perform the following:

1. Click  then type Notifications Event Queue. 

2. Search for failed Notification Events by Event ID or All in the Event field.

3. Tick Processed & Errors to search for only events where an error has been identified and the notification was not sent.

4. Enter the date range in the When From & When To fields, then click .

5. Click the Event ID link to read the log file & identify why the Notification was not sent.


 The information on the right side of the screen provides the following:
FieldDescription
IDDisplays the unique System ID of the event.
WhenDisplays the Date & Time the Event Notification was issued.
UserDisplays the User ID who processed the Event.
Event

Displays the type of event.

(tick) Refer to Event Types for further information.

Notice Type

Displays the type of notification issued. Currently (as at ), only Sales Order Event Notifications can be setup. 

Example: Frameworks.Activity.Notifications.Messages.SalesOrderNotification

LogDisplays the log file.
DataDisplays the datasent for the Event Notification

6. Analyse the log file to attempt to identify why the event notification failed. The log file contains detailed information on failure, however is quite technical to read. 

7. Attempt to resolve the issue, then click to try and reissue the Event Notification that previously failed.

(tick) For assistance, please contact Sterland Computing.

IF THIS FAQ DOESN’T RESOLVE YOUR ISSUE:

Refer to Event Notifications - Setup & Administration and Notification Tasks, then contact Sterland Support.