# Support for truncated ISO-8601 datetimes?

**URL:** <https://cylc.discourse.group/t/support-for-truncated-iso-8601-datetimes/755>\
**Category:** Cylc Development\
**Created:** [September 12, 2023, 5:36am UTC](https://cylc.discourse.group/t/support-for-truncated-iso-8601-datetimes/755 "2023-09-12T05:36:25Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![oliver.sanders](https://yyz2.discourse-cdn.com/free1/user_avatar/cylc.discourse.group/oliver.sanders/32/110_2.png) [@oliver.sanders](https://cylc.discourse.group/u/oliver.sanders)\
**Post date:** [September 12, 2023, 9:04am UTC](https://cylc.discourse.group/t/support-for-truncated-iso-8601-datetimes/755/3 "2023-09-12T09:04:39Z")

</div>

> [@Tip: Cycle Point Format](https://cylc.discourse.group/t/tip-cycle-point-format/685):
>
> Cylc uses the [ISO8601](https://cylc.github.io/cylc-doc/stable/html/tutorial/scheduling/datetime-cycling.html#iso8601) time point syntax for cycle points. For example, this workflow: [scheduling] initial cycle point = 2020 [[graph]] P1Y = @wall\_clock =\> happy-new-year [runtime] [[happy-new-year]] script = echo "Happy ${CYLC\_TASK\_CYCLE\_POINT}!" Will produce cycle points like this: 20200101T0000Z 20210101T0000Z 20220101T0000Z … These cycle points are used to form task IDs and are passed into tasks using the $CYLC\_TASK\_CYCLE\_POINT environment variable: $ cy…

---

_[View the full topic](https://cylc.discourse.group/t/support-for-truncated-iso-8601-datetimes/755)._