...

Each session may contain multiple actions of the above described types. Per default, a session gets committed implicitly by the xUML Runtime when it is terminated without any exception. In this case, all involved transaction resources are committed. Additionally, explicit commits inside a session are allowed for all types of service adapters described above.
If an exception occurred during session execution and if this exception is not being caught, the session gets implicitly rolled back. The xUML Runtime will then rollback all not committed transactions.
However, for all other actions not mentioned in the table above, the session concept does not apply, e.g. file manipulations, external service calls, system adapter calls, and more.

Transaction Id

Each session is identified by a transaction id.

Runtime 2019.9 HTTP header X-Transaction-ID identifies the transaction the call belongs to. You can set the transaction id manually with setTransactionID. If not set, the Runtime will generate one.
This header will be passed through the callstack to identify all service calls that belong to a transaction.

Long-running Transactions

...