# Troubleshooting scheduled event failures

**URL:** <https://community.smartthings.com/t/troubleshooting-scheduled-event-failures/9194>\
**Category:** Writing SmartApps\
**Created:** [January 7, 2015, 4:52pm UTC](https://community.smartthings.com/t/troubleshooting-scheduled-event-failures/9194 "2015-01-07T16:52:23Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![geko](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/geko/32/34862_2.png) [@geko](https://community.smartthings.com/u/geko)\
**Post date:** [January 7, 2015, 9:08pm UTC](https://community.smartthings.com/t/troubleshooting-scheduled-event-failures/9194/5 "2015-01-07T21:08:19Z")

</div>

> [@AaronZON](#):
>
> However, the ‘prev run time’ is always garbage. That is, is says "1969-12. . . . "

This is common Java programming error when converting Unix (epoch) time to Java Date object. The conversion requires explicit casting of epoch time to `long` data type which is often overlooked and results in incorrect Date. I believe this is just a UI issue though.

> I don’t know what I’m looking at in the last column labeled ‘schedule’.

You’re looking at [cron](http://en.wikipedia.org/wiki/Cron) schedule.

---

_[View the full topic](https://community.smartthings.com/t/troubleshooting-scheduled-event-failures/9194)._