Hi,
We have a customer who has been setting up (and building custom) Index Builders for various purposes.
Some instances take several minutes to run and they've set Repository tasks to run at 3:00 am. It turns out that as time goes by we've been seeing the indexes rebuild longer and longer, now being at 10am or 11am.
https://doc.dynamicweb.com/documentation-9/repositories/indexing/tasks
After looking into the logs, I came to the conclusion that the Repeat Interval is based on the End time of the index, not at the Start time of the index. In other words, (making an extreme example), if the index takes 46min to run, the 2nd time it runs will be at 3:50 am, and the next day at 4:40 am and then at 5:30 am (so on and so forth). Instead the customer was expecting it to always start at 3:00 am.
Task: https://www.screencast.com/t/4A8nVQv02u5 and Indexes: https://www.screencast.com/t/APoKfdW87U - in this case notice it started at 01:05 am, despite the task being at 3:00 am
Is this by design? And if so, is there a way we could make the task consider the Start time, rather than Completed time?
Best Regards,
Nuno Aguiar
