Jitterbit EDI AI Monitor (Beta)

Introduction

The EDI AI monitor (Beta) watches your organization's EDI activity and sends an email alert when that activity is unusual compared with its recent history. Examples include a rise in FTP or AS2 failures, an unusual drop in the number of documents exchanged, or transactions waiting too long to be downloaded. This helps you find and fix problems before they affect your trading partners.

The monitor covers FTP, AS2, and transaction activity. It runs alongside document processing and does not delay it.

Alerts are delivered by email and managed from the Management Console Alerts page.

Note

The EDI AI monitor is in beta. To provide feedback, contact the Jitterbit Product Team.

Turn on the EDI AI monitor (Beta)

Each organization that uses Jitterbit EDI has an EDI AI monitor (Beta) alert on the Management Console Alerts page. The alert is paused by default, so you receive no notifications until you resume it. Its recipients are preselected as your Harmony organization administrators (members of a role with Admin permission). The only setting you can change is the list of recipients.

To start receiving notifications, follow these steps:

Use the Harmony portal menu to select Management Console > Alerts. (The Alerts page requires Admin role permission.)
Find the alert with the EDI AI monitor (Beta) event, then hover over its Paused indefinitely status. In the panel that opens, click the Resume icon. For more information, see Resume an alert.
If needed, hover on the alert, then click the Edit icon in the Actions column to change its recipients. Recipients can include registered Harmony users and external email addresses.

To stop receiving notifications, pause the alert again. Pausing keeps the alert and its recipients so you can resume it later.

What the monitor detects

The monitor looks for the following conditions. Each is evaluated for your organization's FTP, AS2, and transaction activity.

Activity	Condition detected
FTP	File transfer failures higher than usual.
FTP	Connection failures higher than usual.
FTP	Number of FTP transfers unusually high or unusually low.
AS2	Messages that fail to send higher than usual.
AS2	Message disposition notification (MDN) failures higher than usual.
AS2	Number of AS2 messages unusually high or unusually low.
Transactions	A document reprocessed more often than usual.
Transactions	Transaction volume unusually high or unusually low.
Transactions	Transactions waiting to be downloaded higher than usual, for example when the schedule that downloads them is turned off.

The monitor tracks each FTP connection and each AS2 connection separately. For transactions, it tracks each combination of company, trading partner, and document type separately.

For failures, reprocessing, and transactions waiting to be downloaded, the monitor alerts only when the count is higher than usual. For the number of transfers, messages, or transactions, it alerts when the count is either unusually high or unusually low.

How the monitor decides activity is unusual

The monitor compares current activity with your organization's own recent history. It compares the current hour with the previous 24 hours and the previous 72 hours, and the current day with the previous week and the previous 30 days. The monitor uses statistical analysis of activity counts, such as the number of transfers, failures, and reprocessed transactions. It does not use a large language model (LLM).

For each comparison, the monitor calculates how likely the current level of activity is, given that history. The less likely it is, the higher the severity of the alert. Severity levels, from lowest to highest, are:

Severity	Likelihood of the current activity
Information	10% or less
Warning	1% or less
Error	0.5% or less
Critical	0.1% or less

Notifications

When the monitor detects unusual activity, it sends an email to the alert's recipients. The subject line shows the alert type and severity, for example Alert Type: FTPVolumeAnomaly Severity: Information.

The email includes the following:

A summary of what was detected.
The observed activity, how it compares with recent activity, and its likelihood. For example, "You have had 3 FTP sessions in the previous hour. This is lower than usual compared with the previous 24 hours (6.5% likelihood)."
The Service Name (for example, FTP or Transaction Volume) and what the alert Applies to. For FTP alerts, this is the FTP connection name. For transaction alerts, it is the company, trading partner, and document type.
Your Harmony Organization and Environment.
Links to the EDI Messages, Connections, and Transactions pages to help you investigate.

Example transaction volume alert

Subject: Alert Type: TransactionVolumeAnomaly Severity: Information

An unusual change in EDI transaction volume has been detected.

You have received 1 transaction in the previous hour. This is lower than usual compared with the previous 24 hours (9.6% likelihood). Company: companyId; Partner: partnerName; Document type: documentType.

Service Name: Transaction Volume
Applies to: companyId:partnerName+documentType

Organization: organizationName
Environment: environmentName

Notifications follow these rules:

You receive one email for each issue. While the issue continues, you receive another email only if its severity increases, for example from Information to Warning to Error.
When activity returns to normal, you receive a resolution email. Its subject begins with Alert Resolution., and its body states that the alert has been resolved and describes the issue that was resolved.
If the monitor doesn't detect the condition again for 2.5 hours, the alert is resolved automatically and you receive a resolution email.

Recommendations

Use the links in the email to check the Messages, Connections (on the Communications page), and Transactions pages, which can help you identify the cause.
Expected changes in activity, such as holidays, month-end processing, or maintenance, can differ from recent history and may trigger an alert. Consider these before taking action.