--- title: "Start Transaction" slug: "commit-transaction" updated: 2023-11-06T15:37:49Z published: 2023-11-06T15:37:49Z canonical: "documentation.decisions.com/commit-transaction" --- > ## Documentation Index > Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt > Use this file to discover all available pages before exploring further. # Commit Transaction | ## Step Details | | --- | | **Introduced in Version** | 4.0.0 | | **Last Modified in Version** | 8.16.0 | | **Modification Details** | Fixed the issue where the Transaction Steps were breaking on migration. | | **Location** | Database > Transaction | The **Commit Transaction** step is used in conjunction with the [Start Transaction](/step-library/docs/start-transaction) step to complete or commit a transaction to a database. Transaction Steps might not work after migrating the project between v8.15 and lower. When migrating a project that includes Transaction Steps to an environment with a version of 8.15 or lower, you may encounter errors. However, this issue has been addressed and resolved in version 8.16 and higher. To ensure a successful migration, specific conditions and steps must be followed. For more information, refer to [Using Transaction Steps](https://documentation.decisions.com/docs/using-transaction-steps). Note:It is important to note that the **Start**, **Commit**, and **Rollback** Steps cannot be utilized independently of each other in a Flow. These three steps must all be used within the same Flow to operate the Transaction or roll back it successfully. #### ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1699284437984.png) --- ## Common Errors ### Missing Start Transaction step The **Commit Transaction** step requires the **Start Transaction** step. If a Start Transaction step is not found along the same path and before the Commit Transaction step, then the step will throw the following error: #### Exception Message: ```cpp Exception Stack Trace: DecisionsFramework.Design.Flow.ErrorRunningFlowStep: Error running step Commit Transaction 1[CommitTransaction] in flow [Testing]: Exception invoking method CommitTransaction on class ORMSteps ---> DecisionsFramework.LoggedException: Exception invoking method CommitTransaction on class ORMSteps ---> DecisionsFramework.LoggedException: cannot commit transaction because we are not in one currently at DecisionsFramework.Data.ORMapper.DynamicORM.Commit(String name) at DecisionsFramework.Data.ORMapper.ORMSteps.CommitTransaction() --- End of inner exception stack trace --- at DecisionsFramework.Design.Flow.StepImplementations.InvokeMethodStep.Run(StepStartData data) at DecisionsFramework.Design.Flow.FlowStep.RunStepInternal(String flowTrackingID, String stepTrackingID, KeyValuePairDataStructure[] stepRunDataValues, AbstractFlowTrackingData trackingData) at DecisionsFramework.Design.Flow.FlowStep.Start(String flowTrackingID, String stepTrackingID, FlowStateData data, AbstractFlowTrackingData trackingData, RunningStepData currentStepData) --- End of inner exception stack trace --- ``` --- Related Information [Using Transaction steps](https://documentation.decisions.com/docs/using-transaction-steps) --- ## Feature Changes | Description | Version | Developer Task | | --- | --- | --- | | Fixed the issue where the Transaction Steps were breaking on migration | [8.16](https://documentation.decisions.com/v99/docs/version-8x) | [DT-039127] |