Developer forum

Hi Imar,

Looking for that too :)

https://doc.dynamicweb.com/forum/cms-standard-features/cms-standard-features/repository-tasks-repeat-interval

+1 from me too.

This comes up often and I was just getting ready to send a nudge on the old threads on this too. It just came up again last week. We want some daily tasks to run at the same time each day rather than shifting through the day over time.

+1

Yep, thanks, that;s how I ended up solving it.

Imare

Hello,

I'm trying to get this to work on V9.16.7. I thought it would work properly after an upgrade, and I tried saving the index task + index but it's still drifting. 

Is there anything else I can try to get this running every 12 hours? Thanks in advance. :)

Hi Skylar,

You should not use the scheduling functionality under the repository setup. It is there for backwards compatibility. Instead, setup a scheduled task under Settings > Integration > Scheduled Task, from where you can use add-in "Build repository index". Then you'll find the drift to disappear.

Hi Morten,

Are you suggesting this as a workaround or the proper way of doing it?

If I understood you correctly, I would almost argue/expect it to work. Based on what you say, we have to create 1 scheduled task for each repository to ensure no "drifts" happen. This means:

• Products
• Users
• Files
• Content
• (all of the above come with Swift for example. customers with multiple sites, shops and custom development may have more)

In my mind this is what's backwards compared to how DW has been doing. For example; there's 1 scheduled task to rebuild User Smart Searches; 1 scheduled task for Email Marketing Scheduler; .... I would expect that would be 1 Task to look for Repositories, and then it would be within the Repositories that we would determine which ones we want to run and when.

That would also mean that we could set permissions on Scheduled Tasks, and have certain users only focused within Repositories.

So, as a workaround this makes sense to me, but I would expect the drift to have been solved. It's also hard to explain to new people on the platform that nuance.

Best Regards,

Nuno Aguiar

Hi Nuno,

It is the proper way. The issue with the scheduler directly under the repository:
Index is set to build every hour at hh:mm 00:00. The build takes 2 minutes to complete. Next job now starts with 2 minutes offset at 01:02. Next again at 02:04. And so forth. This happens due to some time-stamping under Files\System\Diagnostics...

I believe (guessing) it has not been fixed as we would like to have scheduling all in one place, so a fix has not been worth while, as scheduling in time will disappear from this section. You are quite right, though, that Swift is shipped with scheduling directly under Repositories. I will bring this to the Swift team, as it should not be at this location.

BR
Snedker

Hi Morten,

Understood. I'll try to remember the change and focus on DW10 and the new way of doing it.