Message Popups Architecture

Message popups are the main deep-inspection surface for runtime message processing. They combine list filtering, detail analysis, statistics, payload access, and optional AI-assisted investigation.

Related pages

• Modules
• Data Model
• Permissions and Masking
• Flows
• Operations
• Troubleshooting
• Alerting
• Archives
• Tenant Settings

Functional role

The message popup supports:

• operational filtering over message volume
• detailed inspection of one message and its runs
• access to custom headers, attachments, and payloads
• correlation and retry review
• AI-supported error analysis for technical failures

Main APIs

• GET /api/cpi/configMessagesGet/<configId>/
• GET /api/cpi/configMessagesFacets/<configId>/
• GET /api/cpi/messageDetail/<configId>/<messageGuid>/
• GET /api/cpi/messageDetail/<configId>/<messageGuid>/runs/<runid>/
• GET /api/cpi/messageDetail/<configId>/<messageGuid>/attachments/<attachmentId>/
• GET /api/cpi/configs/<configId>/messages/statistics/past-hour/

Entry points

The popup is opened from ConfigOverview.jsx and FocusedConfig.jsx, often preloaded with a status filter, time window, or KPI-derived time range.

Runtime boundary

flowchart LR
    KPI[Overview or focused KPI cards] --> POPUP[MessagePopup]
    POPUP --> LIST[configMessagesGet and facets]
    POPUP --> DETAIL[messageDetail endpoints]
    DETAIL --> RUNS[run details]
    DETAIL --> ATTACH[attachments]
    DETAIL --> PAYLOAD[payloads and related content]
    POPUP --> STATS[past-hour statistics]
    POPUP --> AI[optional AI investigation]

Important dependency

The popup operates on synchronized monitoring data, not on an always-live CPI request path. That means message review quality depends on message sync recency, permission masking, and the completeness of stored related runtime entities.