# Problem in Transaction Groups which is re-created same name **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [May 2, 2023, 6:18am UTC](https://forum.inductiveautomation.com/t/problem-in-transaction-groups-which-is-re-created-same-name/73130 "2023-05-02T06:18:53Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Kisun\_Noh](https://avatars.discourse-cdn.com/v4/letter/k/8dc957/32.png) [@Kisun\_Noh](https://forum.inductiveautomation.com/u/Kisun_Noh)\ **Post date:** [May 2, 2023, 6:18am UTC](https://forum.inductiveautomation.com/t/problem-in-transaction-groups-which-is-re-created-same-name/73130/1 "2023-05-02T06:18:53Z")
Hello, all I have some trouble with a transaction group. I'm using the ignition 8.1.23 version. I erased one transaction group by mistake and re-create the same transaction group named "TriggerWr\_W010" And then I execute transaction groups. It has errored like below the captured image. ![error](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/0/7022d5a0431158413d5289d244d043a39fe2c385.png) It is quite strange, because when I change the Transaction group name, then it works. And I searched for the error. I found some post that has similar symptoms to me. > [@Transaction Group "Fatally Errored" due to scheduled task](https://forum.inductiveautomation.com/t/transaction-group-fatally-errored-due-to-scheduled-task/64662): > > Hello, all I am in the process of validating an upgraded version of Ignition while mirroring the production version of Ignition. These are both housed on different servers, but are looking at the same connections. I noticed for this transaction group, it is giving me a "fatally\_errored" when I try to start it. The error message says there is already a scheduled task for this. Unable to start group. java.lang.IllegalArgumentException: There is already a scheduled task for sql bridge.moldview.m… So, I did that answer which checks the duplicate transaction group folder. but I think It is not duplicated. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/0/e03cd9d295f5f987acea44267556a0158086f121.png) There is no existing named "TriggerWr\_W010". but I found that in the gateways which located the status page - DIAGNOSTICS - EXECUTION (please, see the below image) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/4/e4754cd877fc5d9813210848f4925424bdc51632.jpeg) I think it works if reset or clear a SQL bridge named "TriggerWr\_W010". But, I don't know How to reset the SQL bridge named "TriggerWr\_W010" or Clearing that. Please give me some advice to solve it. ---
**Author:** ![Gabriel\_Hernandez](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/gabriel_hernandez/32/47179_2.png) [@Gabriel\_Hernandez](https://forum.inductiveautomation.com/u/Gabriel_Hernandez)\ **Post date:** [May 11, 2023, 10:48pm UTC](https://forum.inductiveautomation.com/t/problem-in-transaction-groups-which-is-re-created-same-name/73130/2 "2023-05-11T22:48:11Z")
Hi Kisun, Welcome to forums! I think this particular issue would be best taken to Inductive Automation support for help. [https://support.inductiveautomation.com/hc/en-us](https://support.inductiveautomation.com/hc/en-us) ---
**Author:** ![bao.nguyen](https://avatars.discourse-cdn.com/v4/letter/b/8c91f0/32.png) [@bao.nguyen](https://forum.inductiveautomation.com/u/bao.nguyen)\ **Post date:** [March 19, 2024, 4:50am UTC](https://forum.inductiveautomation.com/t/problem-in-transaction-groups-which-is-re-created-same-name/73130/3 "2024-03-19T04:50:39Z")
Hi Kisun, Thank you for pointing me to the Diagnostics/Execution page. I had the same situation - I could start/stop new transaction groups (with a different names to the ones which were erroring). I guess the sql.bridge.\* processes could not stop because the 'mainexec' process kept them running to finish some pending tasks. In my case, I had a few pending Store & Forward items related to those transaction groups. Therefore, I applied the two steps below, and those transaction groups started to work again. 1. Delete all pending Store & Forward items (related to those transaction groups). 2. Restart the gateway (restarting only the SQL Bridge module did not work for me - I guess the 'mainexec' process was controlled by another module). Hope this would be helpful to other people. Kind regards, ---
**Author:** ![Kisun\_Noh](https://avatars.discourse-cdn.com/v4/letter/k/8dc957/32.png) [@Kisun\_Noh](https://forum.inductiveautomation.com/u/Kisun_Noh)\ **Post date:** [March 19, 2024, 5:38am UTC](https://forum.inductiveautomation.com/t/problem-in-transaction-groups-which-is-re-created-same-name/73130/4 "2024-03-19T05:38:12Z")
Thanks for your response. I already clear the issue. I guess, it happens SQL bridge is not updated immediately. which means there is a remaining some cache when deleting or updating transaction groups. So It should be waiting or restarting Ignition what you did.