When anomalies are detected, they are available in Cleo Integration Cloud (CIC) for review. This article explains where to find anomaly data and how to interpret it.
Where to find detected anomalies
Detected anomalies are primarily available in Activity > Anomalies. This view provides a centralized place to review anomaly data across trading partners and document types.
From this page, you can review anomalies at a glance and select individual entries to explore additional detail:
- View anomalies by trading partner and document type
- See when each anomaly occurred
- See whether volume was higher or lower than expected
- Compare actual message counts to the expected volume range
- View the anomaly’s confidence level
What information is shown for each anomaly
Each detected anomaly includes the following information:
| Field | What it shows |
|---|---|
| Date | When the anomaly was detected |
| Anomaly | The type of anomaly detected |
| Partner | The trading partner associated with the anomaly |
| Partner ID | The unique identifier for the trading partner |
| Transaction type | The document type where message volume deviated |
| Actual volume | The number of messages observed |
| Expected volume | The typical range based on historical activity |
This information provides visibility into what changed, not why the change occurred.
Understanding the timeline view
The timeline helps you:
- Visualize normal volume patterns over time
- See how far actual volume deviated from the expected range
- Identify whether anomalies are isolated events or part of a broader trend
Filter and refine anomaly results
The Activity > Anomalies view includes filtering options to help you focus on specific activity.
You can use filters to:
- Narrow results by trading partner or document type
- Limit the time range
- Focus on specific anomaly types or directions
Notifications
Cleo Integration Cloud provides a daily email summary highlighting anomalies detected during the previous 24‑hour period.
Email notifications are managed per user in My Profile, where you can:
- Enable or disable anomaly notifications
- Select which trading partners to include
- Specify which transaction types are included
These settings allow you to tailor notifications to the activity most relevant to your role.
Interpreting anomaly data
Detected anomalies indicate meaningful deviations from expected message volume patterns. They are designed to serve as early warning signals, highlighting changes that might warrant attention.
Keep in mind:
- Anomalies are based on volume only, not transaction content or business impact
- Detection focuses on visibility, not root cause analysis
- An anomaly does not necessarily indicate an error, but it may point to changes in transaction activity that require further investigation
Related information
For an overview of anomaly detection, including how it works and eligibility requirements, see Automated Anomaly Detection for Message Volume.
Comments
0 comments
Please sign in to leave a comment.