3802043 - iFlow message mapping not reflecting new BAPI fields until restart or redeploy, Cloud Integration

• After adding new fields to a custom BAPI structure in the source system, an existing iFlow did not pick up the new fields in one tenant.
• The same iFlow in a QA tenant continued to work without any changes.
• Message mapping became invalid due to missing fields until the iFlow was restarted or redeployed.
• No specific error messages or error codes were reported.

• Cloud Integration

• SAP Integration Suite

cloud integration, integration suite, message mapping, groovy script, cache, iFlow cache, changes not reflected, new fields not picked up, BAPI structure change, redeploy, restart iflow, mapping invalid, runtime cache, script function, tenant difference , KBA , LOD-HCI-PI-OPS , Cloud Operations , Problem