This behavior has been resolved and deployed to the production environment as of 1/14/26.
Description:
If an appointment group is created for a course in one instance in a consortium, but a user logs into a different instance in the consortium, that appointment group will not appear to them. Instead they need to be logged into the exact same consortium instance in order to view these events.
Expected behavior:
The user should see the Appointment Groups in their calendar, regardless of which instance of the consortium they are logged into.
Workaround:
No workaround exists at this time.
Steps to Reproduce:
Prerequisites: Have two instances in a consortium and a student from the one instance enrolled in a course that belongs to the other instance.
- In the course in the second instance, add a teacher and create a group appointment event with a due date.
- As student, log into the first instance, not the instance the course belongs too.
- Go to the calendar and notice that the events created in Step 1 are not appearing.
- Now, instead login as the student into the same instance that the course belongs too and navigate to the calendar, notice it now is appearing.
