RunIn Scheduled a Job with no Next Run Time

Anyone ever seen a runIn result in an empty schedule:

The function it is running is very simple and has worked dozens of times before and after unscheduling and running again, worked the next time. The function is fairly straight forware:


I just didn't think that it was possible to get a scheduled job with no time set. Does anyone have any idea what could have caused something like this? I've gone back through the logs and don't see anything.

Update: Could this possibly be due to the hub being down at the time of the event? I know that scheduled jobs will persist after a reboot, but what happens if the time for those scheduled jobs has passed when the hub reboots? I know they don't get run when the hub boots. But I would have thought that they would be cleaned up and thrown away. But it looks like that might not be the case after all. How can I check to see if I have this happening so I can clean it up in my app? Can I recall scheduled jobs? I've never tried to do that before.