version 0.11.3: So I have a pipeline that is normally ran on a schedule for 8:05 am, but didn't actually run due to network drop. So after daemon was re-launched, the pipeline didn't actually run until 11:11am. Not sure what the tick history is suppose to show, but it is showing that pipeline ran at 8:05am. Is that expected or normal?

@daniel / @prha

Taking a look…. I think we have only one timestamp field, and in the case of schedules it represents the logical timestamp (when it was supposed to run) as opposed to the actual execution time. I think we should probably switch this to be the execution time and then add the logical time as metadata?

Sure @prha! Will do.