Message Tracking
The TrackLog provides complete visibility into all AS2 message transactions - both sent and received. Search, filter, and troubleshoot message exchanges.
TrackLog Overview
Every AS2 transaction is logged in the TrackLog, including:
- Unique message ID
- Sender and receiver AS2 IDs
- Transaction status
- Timestamps for creation and last update
- Links to EDI content and MDN receipts
Searching and Filtering
Use the filters to find specific transactions:
- Search by ID - Enter a full or partial message ID
- Filter by Status - Show only successful, failed, or pending messages
- Date Range - Filter transactions within a specific time period
Transaction Operations
| Operation | Description |
|---|---|
| Copy EDI URL | Get a pre-signed S3 URL to download the original EDI content |
| Copy MDN URL | Get a pre-signed S3 URL to download the MDN receipt |
| Error Msg | View detailed error information for failed transactions |
Message Status Reference
Messages progress through various statuses during sending and receiving. The status indicates the current state of message processing.
Outbound (Sending) Statuses
| Status | Code | Meaning |
|---|---|---|
| Waiting to Encrypt | 21 | Message queued for encryption processing |
| Original File Saved | 22 | Original EDI file archived to S3 |
| Encryption Success | 23 | Message encrypted successfully |
| Send Success | 24 | Message sent to trading partner's AS2 endpoint |
| MDN Received | 25 | MDN receipt received and decrypted successfully |
| MDN Saved | 26 | Message delivered successfully, MDN receipt stored in S3 |
Inbound (Receiving) Statuses
| Status | Code | Meaning |
|---|---|---|
| Wait to Decrypt EDI | 11 | Incoming message queued for decryption |
| Decrypt EDI Successfully | 12 | Message decrypted and signature verified |
| Save Decrypt EDI to S3 Successfully | 13 | Decrypted EDI file saved to S3 |
| Create EDI to S3 Successfully | 14 | MDN generated and saved to S3 |
| Send MDN Successfully | 15 | MDN receipt sent back to sender |
EDI Transformation Statuses
| Status | Code | Meaning |
|---|---|---|
| Parse EDI Successfully | 60 | EDI document parsed to JSON successfully |
| Transform to EDI Successfully | 70 | JSON transformed to EDI format successfully |
Error Statuses
| Status | Code | Meaning |
|---|---|---|
| Decryption Failed | 31 | Failed to decrypt incoming message |
| Decrypt MDN Error | 32 | Failed to decrypt MDN receipt |
| Encryption Failed | 41 | Failed to encrypt outgoing message |
| Encrypt MDN Error | 42 | Failed to encrypt MDN receipt |
| Send Failed | 52 | Message delivery failed - check error details |
| Parse EDI Error | 61 | Failed to parse EDI document |
| Transform to EDI Partnership Not Exists | 71 | Partnership not found for EDI transformation |
| Transform to EDI Error | 72 | Failed to transform JSON to EDI |
| Partnership Not Found | 91 | No matching partnership configuration found |
| AS2 Exception | 92 | AS2 protocol processing error |
| Unknown Status | 99 | Unknown or unhandled error |
| AS2 Exception | 999 | Critical AS2 processing exception |
Status badges are color-coded: Green indicates success (codes 20-29), Gray indicates in-progress or waiting, and Red indicates errors (codes 30+).
Troubleshooting Failed Messages
When a message fails, click "Error Msg" to see details. Common issues include:
- Connection timeout - Partner's endpoint is unreachable
- Certificate error - Expired or mismatched certificates
- Decryption failed - Wrong encryption key or algorithm mismatch
- Signature verification failed - Certificate mismatch
Transaction logs and EDI content are retained based on your configuration. Default retention is 90 days. Adjust in your DynamoDB TTL settings if needed.