# Transaction Groups Execution Scheduling Speed **URL:** \ **Category:** Ignition\ **Created:** [October 4, 2018, 10:17pm UTC](https://forum.inductiveautomation.com/t/transaction-groups-execution-scheduling-speed/19984 "2018-10-04T22:17:34Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![dion.botha](https://avatars.discourse-cdn.com/v4/letter/d/46a35a/32.png) [@dion.botha](https://forum.inductiveautomation.com/u/dion.botha)\ **Post date:** [October 4, 2018, 10:17pm UTC](https://forum.inductiveautomation.com/t/transaction-groups-execution-scheduling-speed/19984/1 "2018-10-04T22:17:34Z")
Hi guys, I want to use Ignition as a tool to diagnose an intermittent (happens about once a day) anomaly in one of our machines. My approach is to log a few Boolean OPC tags in a historical transaction group when the values change. My question is should I be worried about using a 1 millisecond execution schedule? If so, how can I figure out the fastest execution schedule I can run without worry? Regards, D.Botha ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [October 4, 2018, 10:49pm UTC](https://forum.inductiveautomation.com/t/transaction-groups-execution-scheduling-speed/19984/2 "2018-10-04T22:49:51Z")
Depends what protocol and device you’re trying to get this data from, but 1ms is probably too fast to get reliably. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [October 4, 2018, 11:10pm UTC](https://forum.inductiveautomation.com/t/transaction-groups-execution-scheduling-speed/19984/3 "2018-10-04T23:10:39Z")
> [@Kevin.Herron](#): > > but 1ms is probably too fast to get reliably. Even if you can get a transaction group to run that fast, you are unlikely to get an OPC driver to run that fast. This is a job for the PLC to do. ---
**Author:** ![dion.botha](https://avatars.discourse-cdn.com/v4/letter/d/46a35a/32.png) [@dion.botha](https://forum.inductiveautomation.com/u/dion.botha)\ **Post date:** [October 8, 2018, 2:45pm UTC](https://forum.inductiveautomation.com/t/transaction-groups-execution-scheduling-speed/19984/4 "2018-10-08T14:45:24Z")
Hi guys, thanks for the replies - job for the PLC makes sense but I would still like to know if there are any implications of running transaction groups too fast. ---
**Author:** ![Mr.K001](https://avatars.discourse-cdn.com/v4/letter/m/ea5d25/32.png) [@Mr.K001](https://forum.inductiveautomation.com/u/Mr.K001)\ **Post date:** [October 9, 2018, 9:45pm UTC](https://forum.inductiveautomation.com/t/transaction-groups-execution-scheduling-speed/19984/5 "2018-10-09T21:45:36Z")
I mean I don’t think there is any implications but 1ms is just too fast and besides, what’s the point of 1ms schedule time if your tag scan class is not 1ms(or faster) because if it’s not then you’re wasting time scanning the tag every 1ms when the tag itself isn’t even being scanned that fast. I suggest you set your tag scan class to 1sec and set your transaction group to 500ms and let it run for a day or so and see what kind of info you get. If the issue that you are having happens that darn fast that you feel like you might miss it if you don’t scan it every 1ms then maybe you should latch those BOOL tags for a few seconds when they come on and then unlatch them (if the tags are coming from a PLC). This way you don’t have to scan them that fast. Just my two cents 😁 Good luck! 👍