# Delay between lines of code

**URL:** <https://forum.inductiveautomation.com/t/delay-between-lines-of-code/77301>\
**Category:** Ignition\
**Tags:** ignition81, scripting\
**Created:** [August 2, 2023, 6:31pm UTC](https://forum.inductiveautomation.com/t/delay-between-lines-of-code/77301 "2023-08-02T18:31:39Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [August 2, 2023, 7:15pm UTC](https://forum.inductiveautomation.com/t/delay-between-lines-of-code/77301/11 "2023-08-02T19:15:01Z")

</div>

As Phil already mentioned - if you want control over execution, scheduling, and to have a guarantee when something is done, considering dropping the transaction group entirely in favor of a script:

> [@Transaction groups Schedule (Day)](https://forum.inductiveautomation.com/t/transaction-groups-schedule-day/77089/9):
>
> That's not what I meant. I meant to not have a transaction group, just a script that does the operations that a transaction group would do.

---

_[View the full topic](https://forum.inductiveautomation.com/t/delay-between-lines-of-code/77301)._