# Driving Execution At a Fixed Rate

**URL:** <https://forum.inductiveautomation.com/t/driving-execution-at-a-fixed-rate/74325>\
**Category:** Module Development\
**Created:** [May 31, 2023, 2:26am UTC](https://forum.inductiveautomation.com/t/driving-execution-at-a-fixed-rate/74325 "2023-05-31T02:26:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nicholas.robinson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nicholas.robinson/32/22188_2.png) [@nicholas.robinson](https://forum.inductiveautomation.com/u/nicholas.robinson)\
**Post date:** [May 31, 2023, 2:26am UTC](https://forum.inductiveautomation.com/t/driving-execution-at-a-fixed-rate/74325/1 "2023-05-31T02:26:19Z")

</div>

If I want to drive an action in a module to happen say every 1 minute, is the following a valid way to do it?

```auto
gatewayContext.getExecutionManager().registerAtFixedRate({params})

```

Or, what is everyone's best practices for driving repeated actions/checks at a certain rate inside a module.

Thanks,

Nick

Edit: would be combined with a runnable

---

<div class="post-metadata">

**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:** [May 31, 2023, 11:48am UTC](https://forum.inductiveautomation.com/t/driving-execution-at-a-fixed-rate/74325/2 "2023-05-31T11:48:07Z")

</div>

Yes, that's the simplest answer. If you expect substantial load with many such tasks, consider making your own executor service with a dedicated thread pool.