Message Popup Reference
This page is the short working reference for people who inspect CPI messages in the product.
What the popup helps you answer
- Which messages match the current problem?
- Which status, headers, or timestamps stand out?
- Is payload content available or intentionally masked?
- Are there related runs, attachments, or correlated messages?
Message detail matrix
| Area | What it shows | What users usually do next |
|---|---|---|
| List view | matching messages in the current configuration | narrow with filters or open one row |
| Detail panel | full message context for one message | inspect error, timestamps, and relations |
| Runs | processing attempts and runtime progress | compare retries or failures |
| Payloads | stored payload metadata and, if allowed, content | inspect body or confirm masking |
| Attachments | related technical files and exports | download or inspect cache state |
| Correlation | messages that belong to the same business chain | follow the wider incident |
Practical value guide
| Value or signal | What it usually means |
|---|---|
FAILED | the message ended with an error and needs review |
COMPLETED | the message finished successfully |
RETRY | processing was retried or is in retry-related handling |
payload count greater than 0 | payload metadata exists for this message |
runs count greater than 0 | runtime run information is available |
correlation count greater than 1 | the message is part of a larger chain |
Why payloads may be hidden
Payload content is not always visible even when a message row exists.
Typical reasons:
- payload access is restricted for your role or scope
- payload download is disabled or limited for the tenant
- the payload metadata exists, but the body was not cached yet
Typical daily actions
| Goal | Fastest product action |
|---|---|
| find one failed message | filter by status and time range |
| compare retries | open the run list of the affected message |
| inspect business context | check correlation and custom headers |
| verify whether payload access is allowed | open payload metadata and look for masking |
Quick operator checks
- Is the issue visible in one message or across a correlation group?
- Are you looking at the current configuration and time range?
- Is the missing information truly absent, or only masked?
- Do runs, payloads, and attachments tell the same story?
Shared product context
For common visibility, masking, and cross-module state meanings, see Product Reference and Shared Product Values.
Need the deep technical view?
See: