# Tasks - Cron Offset

**URL:** <https://community.influxdata.com/t/tasks-cron-offset/20820>\
**Category:** InfluxDB 2\
**Tags:** flux\
**Created:** [July 19, 2021, 5:53pm UTC](https://community.influxdata.com/t/tasks-cron-offset/20820 "2021-07-19T17:53:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Patrick808](https://avatars.discourse-cdn.com/v4/letter/p/b487fb/32.png) [@Patrick808](https://community.influxdata.com/u/Patrick808)\
**Post date:** [July 19, 2021, 5:53pm UTC](https://community.influxdata.com/t/tasks-cron-offset/20820/1 "2021-07-19T17:53:40Z")

</div>

Per documentation:

## [offset](https://docs.influxdata.com/influxdb/cloud/process-data/task-options/#offset)

> Delays the execution of the task but preserves the original time range. For example, if a task is to run on the hour, a `10m` offset will delay it to 10 minutes after the hour, but all time ranges defined in the task are relative to the specified execution time.

This does not appear to be the case; with the following I get times that are one minute after the hour:  
`option task = {name: "task-Hourly", cron: "0 * * * *", offset: 1m}`

Is there a workaround for this, or am I missing something? I need my data windowed relative to the hour, but I have to run multiple tasks on the data some hours of the day.

---

<div class="post-metadata">

**Author:** ![Anaisdg](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/anaisdg/32/6401_2.png) [@Anaisdg](https://community.influxdata.com/u/Anaisdg)\
**Post date:** [July 21, 2021, 5:36pm UTC](https://community.influxdata.com/t/tasks-cron-offset/20820/2 "2021-07-21T17:36:24Z")

</div>

Hello @Patrick808,  
How are you querying your data?  
Also can you use the every option instead?  
So that you can query your data with range(start: -task.every)?
