Database Notifications
Preface
All of these alerts will require system administrator database access to set them up as they run cyclically via the SQL Agent.
EDI Queue Alerts
The standard setup for these alerts is for the SQL agent to run the respective stored procedure every 15 minutes*.
Intermediary Alerts
This runs the stored procedure ENG.CrossfireQueue_Intermediary_Alert, which will trigger the alert to report on a per partner basis:
Interchanges in the decompiling state
Messages in the processing or compiling states
If they have been stuck in either state for 30 minutes*. E.g. if there is a interchange in the decompiling status for partner A for over 30 minutes then an alert will be generated
Waiting Alert
This runs the stored procedure ENG.CrossfireQueue_Alert, which will trigger the alert to report on a per partner basis:
Interchanges in the received or compiled
Messages in the decompiled or built
If they have more than 500 interchanges/messages* in each state or if the oldest message/interchange in each state is older than 10 minutes*. E.g. if there are over 500 messages for partner A in the built status then an alert will be generated OR if there is a interchange in the compiled status for longer than 10 minutes then an alert will be generated.
* These values are all configurable