Rollback on Error Behaviour in Integration Procedures with HTTP Action

When a Parent Integration Procedure (IP) has rollback on error enabled and includes two child IPs—one performing an HTTP POST action and another executing a DML operation—an issue can occur during execution. The parent IP creates a savepoint within the initial transaction (T1). However, the HTTP child IP executes asynchronously using a Continuation/async context, which causes it to run in a new transaction (T2).

If the subsequent child IP fails due to a DML validation error, the parent attempts to roll back to the savepoint created in transaction T1. Since this savepoint belongs to a different transaction than the current one, the rollback fails and results in the following error:

java.lang.IllegalStateException: Programmer error: cannot rollback to savepoint on another transaction

Simple configuration of Parent Integration procedure:
- The parent IP has two child Ips- one with HTTP action and other with datamapper post action with rollback on error enabled 
-The Child IP has a HTTP action doing the post action
-The second child IP has a datamapper load action(DML operation)