Use Datastore to avoid too many duplicate MPL attachments in exception retries
Walks through an Integration flowsIntegration flowsMoving and transforming messages between systems in middleware instead of in application code: an integration flow with its adapters and mappings, and the runtime it executes on. Reaching a remote system from application code is destinations, and brokering events between systems is Event Mesh.SAP only design on Cloud IntegrationCloud IntegrationBuilds and runs integration flows that process, route and map messages between cloud and on-premise systems, SAP and non-SAP, through prebuilt adapters; available only under an SAP Integration Suite plan.sap official, btp: an exception subprocess that writes the source and in-flight payloads to a DataStore entry, keyed by the message's correlation header and overwritten on each retry, instead of a Groovy script attaching both payloads to the message processing log on every run. With unrestricted retries left in place, one interface the author retried 14 times produced two DataStore entries instead of up to 28 message processing log attachments; the post also notes that deleting the DataStore entry for a retrying message marks it Cancelled in monitoring without stopping the retries.
Where it sits
Who is behind it
Properties
About this work
For integration-flows
Details
Graph
Source
History
- Entered the atlasDiscovered via SAP Community · integration-suite-tag.
For your agent
- Ref
content:use-datastore-to-avoid-too-many-duplicate-mpl-attachments-in-exception-retries- JSON
- /content/use-datastore-to-avoid-too-many-duplicate-mpl-attachments-in-exception-retries.json
- MCP
- Connecting an agent