When setting up a Clarity task on a scheduled time, there are some things to keep in mind.

• Scheduled tasks are controlled by the Clarity Monitoring Service that runs on the host.

  • If the Monitoring service is not running, scheduled tasks will not run.

• Tasks must be set to Enabled ‘Yes’
• The time the tasks run is based on the equivalent time in the host timezone.
• If the task is set to ‘Only on Change’
  • Has the model date changed since the last time the task was run? (using the date as shown on the project homepage)
  • Has the task definition been changed/saved since the last time the task was run?
  • In the case of a project-scoped task, if any model in the project has changed, the project is considered changed.
• Notes:
  • The updates to the date last modified shown on the project homepage are performed by the monitoring service, and they are updated on different schedules according to the project type (ranging from near-instantaneous to once every 45 minutes or so). In the case of BIM360 projects, there are also different date updates that Clarity receives - in some cases for Publish Dates and in some cases for the last Sync To Central.
  • The date modified only refers to the file itself, it does not consider if there is a link within the file which has changed.

Schedule Settings

The time you see on the Task Configuration page next to the Schedule represents your timezone

This is to make it easier for you to schedule tasks based on your timezone.

If you hover over your timezone shown above, it will show you the difference between your timezone and the host, if any.  In my case there isn’t one.

However, tasks are always run off what the scheduled time equates to on the host.

Example

If you schedule a task to run at 9:00 pm (21:00) PST and the host is on EST, the task will run at midnight EST since there is a three-hour difference between those two time zones.

That is when the task will be “launched” and placed in the queue.

If the task server that picks it up is in Texas, that task is running on that task server at 10:00 pm since Texas is in the Central time zone.