iGlow / Fix failed messages
Guide · Fix
Fix failed messages in SAP CPI with AI
Updated · by the iGlow team at StellarClouds
Short answer: In iGlow's side panel, pick a failed message and click Fix. iGlow reads the error, the failing step, the script and the trace, and explains the root cause. If the fix belongs in a Groovy script, XSLT or mapping, it proposes a small change as a diff; you approve it, and iGlow saves it after taking a snapshot. Other problems, such as credentials or certificates, are explained with next steps.
Steps
- See what failed. The panel home lists your tenant's recent failed messages, from the last 24 hours or, when it has been quiet, up to the last 7 days. Each one has a label such as Script error or Receiver rejected call, before you open it.
- Click Fix on a message. iGlow gathers the error text, the step that failed, the script or mapping, and a short trace excerpt if one exists.
- Read the root cause. iGlow explains in plain words what went wrong and where.
- Review the patch. For code problems you get a minimal diff with the reason. Approve, edit or reject it.
- Save, test and deploy. iGlow takes a snapshot, saves the change, can simulate it, and deploys when you confirm. Undo restores the snapshot.
Fixed with a reviewed patch
- Null values and missing fields in Groovy scripts
- Type, cast and number-format errors
- Empty or malformed payloads reaching a script
- XSLT errors such as sequences and empty values
- Typos and undefined variables
- Message Mapping steps that SAP reports as "Mapping file not found"
Explained with next steps
- Receiver errors such as 401 or 500 responses
- Expired or missing certificates and keystore entries
- Missing credential aliases and secure parameters
- Timeouts, DNS and Cloud Connector issues
- Configuration and externalized parameters
What is sent to the AI
Only what the fix needs: the error, the step, the script and a short trace excerpt. Emails, phone numbers, card and IBAN-like numbers, tokens and authorization headers are masked in your browser first, and the panel shows exactly what was sent. See the privacy policy.
Questions
How do I find why a message failed in SAP CPI?
Open the message in Monitor and look at the error and the failing step. iGlow does this for you: it labels every failed message with its likely cause and, when you click Fix, explains the root cause from the error, step, script and trace.
Will iGlow change my iFlow without asking?
No. Every save and deploy needs your click, iGlow takes a snapshot before each change, and tenants tagged PRD are never changed.