# What are the BEGIN and COMMIT/ROLLBACK rules of engagement?
**URL:** https://matillioncommunity.discourse.group/t/what-are-the-begin-and-commit-rollback-rules-of-engagement/2087
**Category:** Matillion ETL
**Created:** [March 13, 2023, 2:45pm UTC](https://matillioncommunity.discourse.group/t/what-are-the-begin-and-commit-rollback-rules-of-engagement/2087 "2023-03-13T14:45:11Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@gjohnson3](https://matillioncommunity.discourse.group/u/gjohnson3)
#### Post date: [March 13, 2023, 2:45pm UTC](https://matillioncommunity.discourse.group/t/what-are-the-begin-and-commit-rollback-rules-of-engagement/2087/1 "2023-03-13T14:45:11Z")
Matillion version 1.68.3 on AWS hitting Snowflake, and my transactions are off the rails...
I've got my begins and commits where I want them, but somehow, they're not "lining up". The first COMMIT can't _find_ the transaction, and the subsequent BEGIN bumps into it!
Can someone please explain what's happening, or how I can get these transactions to work?
Snowflake supports named transactions, but the BEGIN component doesn't exploit this. It seems like this would solve the problem, no? Being able to COMMIT an open transaction by name would be unambiguous.
I would love to see what design patterns are working for all of you!
---
### Author:  [@gjohnson3](https://matillioncommunity.discourse.group/u/gjohnson3)
#### Post date: [March 13, 2023, 2:48pm UTC](https://matillioncommunity.discourse.group/t/what-are-the-begin-and-commit-rollback-rules-of-engagement/2087/2 "2023-03-13T14:48:16Z")
... and the full pull for context
---
### Author:  [@gjohnson3](https://matillioncommunity.discourse.group/u/gjohnson3)
#### Post date: [March 13, 2023, 2:52pm UTC](https://matillioncommunity.discourse.group/t/what-are-the-begin-and-commit-rollback-rules-of-engagement/2087/3 "2023-03-13T14:52:35Z")
The point of the transaction in the RAD job is that the "Recent History" step does DML work that needs to be committed (or rolled back) with the work done in the iterations of RAD\_Delta.
---
### Author:  [@GrantCulp](https://matillioncommunity.discourse.group/u/GrantCulp)
#### Post date: [March 15, 2023, 1:31am UTC](https://matillioncommunity.discourse.group/t/what-are-the-begin-and-commit-rollback-rules-of-engagement/2087/4 "2023-03-15T01:31:39Z")
Hey, I cant diagnose your issue specifically but we use transactions in our jobs as well. We have had a bunch of issues with it. Something that did help was only putting transformation jobs in transaction blocks.
---
### Author:  [@AnudeepK](https://matillioncommunity.discourse.group/u/AnudeepK)
#### Post date: [March 17, 2023, 5:58am UTC](https://matillioncommunity.discourse.group/t/what-are-the-begin-and-commit-rollback-rules-of-engagement/2087/5 "2023-03-17T05:58:24Z")
Hi there, we have a similar problem here, when we are executing parallel transformations using transactional blocks. Raised an idea in the portal, please keep up-voting it .
[Idea: Name Transaction Control Components (Begin, Commit, Rollback) (matillion.com)](https://metlcommunity.matillion.com/s/idea/0874G000000XoG4QAK/detail)