Symptom
- An iFlow is being triggered automatically by a Start timer event. The iFlow is shown as 'Started' in the Manage Integration Content Monitor but it does not appear to run - there are no corresponding messages being generated on the Monitor Message Processing page
OR - An iFlow is being triggered by calls being made to a Sender Adapter. The HTTP Access logs indicate that the call successfully reaches the adapter (either a 200 or 202 response is returned) but the iFlow does not appear to run - there are no corresponding messages being generated on the Monitor Message Processing page
Read more...
Environment
- SAP Cloud Integration
- SAP Integration Suite
Product
Cloud Integration all versions ; SAP Integration Suite all versions
Keywords
CPI, Cloud Integration, MPL, Message processing log, Messages, Message Monitor, processing, running, started, deployed, SCPI, tenant, log level, logs, traces, iFlow, integration flow , KBA , LOD-HCI-PI-RT , Integration Runtime , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.