Overview
When you assign a course or Learning path through an automated assignment rule, the due date is calculated based on the time zone of the user who owns the assignment rule. This helps ensure that the due date reflects the assignor’s intended end-of-day deadline.
Because learners may have different time zones set in their profiles, the date displayed to each learner may vary depending on their own time zone.
Scenario
You create an assignment rule for a course or Learning path and set the due date to 1 day after assignment.
For example, if the rule assigns training on April 22 and the assignor is in a time zone such as GMT-7, the due date is calculated as the end of the next day in the assignor’s time zone: April 23 at 23:59:59 GMT-7
To store and display this accurately across different time zones, the platform converts that due date to UTC. In this example, the stored due date becomes: April 24 at 06:59:59 UTC
As a result:
- A learner in the same time zone as the assignor may see the due date as April 23.
- A learner in UTC may see the due date as April 24.
Both dates represent the same exact due date timestamp, displayed according to each user’s time zone.
Why This Happens
Due dates are stored as exact timestamps, not only as calendar dates. The platform uses the assignor’s time zone to determine the intended end-of-day deadline, then converts that value for each learner based on their own time zone settings.
Since the user interface displays due dates as dates, without the full time component, two users in different time zones may see different calendar dates for the same assignment deadline.
What You Can Check
If you notice that learners assigned by the same automated rule see different due date dates, you can review the following:
-
The assignment rule due date setting
Confirm how many days after assignment the rule is configured to use. -
The assignor’s time zone
The due date is based on the time zone of the user associated with the assignment rule. -
The learner’s time zone
The date shown to the learner reflects the learner’s selected time zone.
The key point is that due dates created through automated assignment rules are based on the assignor’s time zone and then displayed according to each learner’s time zone. Because of this, the same due date may appear as different calendar dates for learners in different time zones.
Recommended Guidance
When reviewing due dates created by automated assignment rules, keep in mind that the date shown to a learner is personalized based on time zone settings.
If the due date appears to be one calendar day later for a learner, this may simply reflect that the assignor’s end-of-day deadline falls on the next calendar date in the learner’s time zone.
To support consistent expectations, make sure that administrators and learners have the correct time zone selected in their profiles. This helps due dates display in the most relevant local context for each user.
Key Takeaway
Automated assignment rule due dates are calculated using the assignor’s time zone and displayed using each learner’s time zone. As a result, the same deadline may appear as different calendar dates for different users, especially when their time zones are not the same.
Related Articles