> For the complete documentation index, see [llms.txt](https://docs.rierino.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rierino.com/devops/api-event-and-process-flows/configuring-saga-steps/event-step/flow-actions/perform-db-transaction.md).

# Perform DB Transaction

These actions provide ability to execute multiple state manipulation journals as a single database transaction.

## Perform DB Transaction Actions

### ExecuteTransaction

Executes database statements on target JDBC state managers as a single transaction, using an array of journals provided in the `journals` path of the event payload.

### StartTransaction

Starts a database transaction on the current local thread, which can be used as part of a local saga flow for multiple database operations.

### CommitTransaction

Commits the current database transaction started on the local thread. Call this after `StartTransaction`.

### RollbackTransaction

Cancels and rolls back the current database transaction started on the local thread. Call this after `StartTransaction`.

{% hint style="info" %}
This handler can only be used on JDBC state managers.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rierino.com/devops/api-event-and-process-flows/configuring-saga-steps/event-step/flow-actions/perform-db-transaction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.