Managing Transactions in the RAI Console
Database transaction activity can be viewed, analyzed, and managed in the RAI Console.
To manage transactions, click the Transactions clock icon on the left-hand side of the Console. The Transactions page opens:
Within this page, you have access to all transactions associated with the selected RAI account. This includes transactions initiated via the Console or any of the RelationalAI SDKs.
You can inspect the details of all past and currently running transactions. Running transactions can also be canceled. For more details, see Canceling a Transaction.
Transaction information are stored and are accessible for transactions up to 30 days. Older transactions are not accessible.
Viewing Transaction Activity
When the Transactions page opens, it displays only transactions that you have initiated.
To view transactions for your entire account, click All Transactions next to the Search field.
To return to viewing only your transactions, click Yours.
Transaction Activity Table
The following transaction details are shown in the Transaction Activity table.
| Field | Explanation |
|---|---|
| DATABASE NAME | Database in which the transaction ran. |
| ENGINE NAME | Engine on which the transaction ran. |
| QUERY | The actual query executed by the transaction. |
| STATE | Current state of the transaction. See Transaction States for details. |
| CREATED ON | Time when the transaction was initiated. |
| FINISHED AT | Time when the transaction completed. |
| DURATION | Amount of time the transaction took to run. |
| READ-ONLY | Whether or not the transaction was read-only. |
To inspect a transaction and get more detailed information, select the transaction by clicking it.
Searching for Transactions
You can search for transactions by entering text in the Search box. Search conducts a fuzzy, client-side search on all columns.
Search only returns results for transactions already displayed; it will not return results for earlier transactions.
Inspecting a Single Transaction
You can view detailed information on a transaction, which looks like this:
The Transactions detail page displays the following information:
| Status | Explanation |
|---|---|
| Transaction | Status and details of the transaction. See Transaction States for more information. |
| Query | The executed Rel program (first 1000 characters). |
| Results | Results of the transaction (if applicable). |
Transaction States
Transactions can be in one of four states:
| Status | Explanation |
|---|---|
| Created | Transaction has been issued but is not yet running. |
| Running | Transaction is currently running. Running transactions can be canceled. |
| Completed | Transaction has run successfully. |
| Aborted | Transaction has been canceled by the user or aborted by the system. See Abort Reasons below for more details. |
Transaction Details
| Field | Explanation |
|---|---|
| Id | Unique identifier for the transaction. Useful for communicating with RAI support. |
| Database | Database in which the transaction ran. |
| Engine | Engine on which the transaction ran. |
| State | Current state of the transaction: Created, Running, Completed, or Aborted. |
| Abort Reason | If transaction was aborted, reason why. See Abort Reasons below for more details. |
| Created On | Time when the transaction was initiated. |
| Finished At | Time when the transaction completed. |
| Duration | Amount of time the transaction took to run. |
| Read-only | Whether or not the transaction inserted or deleted base relation data. |
| Format Version | Version of the SDK used. Best practice is to use the latest version of the SDK. |
| User Agent | Name of SDK or the browser details when executed via the Console. |
| Tags | Displays metadata attached to a transaction via SDKs. For more information, contact support@relational.ai. |
| Datadog | Internal option for inspecting transactions. |
Abort Reasons
| Abort Reason | Explanation |
|---|---|
| Canceled | Transaction was canceled by user. |
| Engine Shutting Down | Engine was shut down before transaction could complete. |
| Integrity Constraint Violation | Transaction canceled because query violates an integrity constraint. See Integrity Constraints for more details. In these cases, the transaction still shows results, so that you can debug the query. |
| Invalid Request | Transaction resulted in an invalid request to the server. |
| Runtime Error | Transaction aborted because the computation of a requested relation triggered a runtime error. |
| System Internal Error | System has experienced an error. |
Canceling Transactions
While a transaction is running, you can cancel it by clicking Cancel in the far right-hand column. Canceled transactions will eventually move to an aborted state.
If a transaction happens to complete before the system processes the cancellation, it may move to a completed state.