Resolving Rooster's Automated task failures

This guide will talk about resolving Rooster's automated tasks failures

• Failed to transfer contacts due to a duplicated MCR

• Failed to transfer contacts due to start date of next posting being earlier than end date of current posting

• Failed to transfer contacts due to missing end date

• Failed to disable a contact due to references in routing rules or rosters

• Failed to disable a contact due to references in broadcast groups

Failed scheduled transfer of contacts

A scheduled transfer can fail due to several reasons. If a scheduled transfer isn’t completed by its intended date, relevant admins will be notified via email. We will explain the reasons for these errors below and provide guidance on how to resolve them.

Scheduled transfer failed due to a duplicated MCR

If there are conflicting MCR values in the 'Current Main Posting' or 'Next Main Posting' with an existing contact in the directory, the contact transfer will fail.

How can you resolve this issue?

To troubleshoot this issue , you can:

1. Ensure you are in the right institution as mentioned in the header of the email.

1. Search for the contact by name or MCR number as displayed in the email (e.g ayushi, M12335X) on the 'Directory' page on Rooster.

2. Click on 'Next Postings' to modify the MCR number which was causing the issue. Click 'Save' after modifying the details.

3. Ensure this MCR number is not duplicated by searching for it in the Directory page.

4. If no further errors arise, this contact will be transferred accordingly the next day.

Scheduled transfer failed due to start date being earlier than end date

Even though we display a warning message when adding posting details to prevent users from selecting a start date for the next posting earlier than the end date of the current posting, errors can still occur.

Screenshot of error to email if current main posting end date is later than next posting start date

How can you resolve this issue?

To troubleshoot this issue , you can:

1. Find the contact by searching by name or MCR number as displayed in the email (e.g ayushi, M19245X) on the 'Directory' page on Rooster.

2. Click on 'Next Posting' and ensure your start date is later than your end date date. Click on 'Save' after modifying your details.

3. If no further errors arise, this contact will be transferred accordingly the next day.

Scheduled transfer failed due to missing end date

Current posting’s End date is needed to transfer a contact from one institution to another. A warning message will be displayed if this end date is missing. On the start date of the next posting, if this information is missing the transfer will fail and an email will be sent to the next posting institution’s email.

Error displayed on Rooster interface

Screenshot of email sent for schedule transfer failing due to duplicated MCR number

How can you resolve this issue?

To troubleshoot this issue , you can:

1. Search for the contact by name or MCR number as displayed in the email (e.g ayushi, M19245X) on the 'Directory' page on Rooster.

2. You will need to contact the institution found under 'Current Posting' and ask them to input the end date of this contact.

3. Once the end date has been successfully added, this contact will be transferred accordingly the next day.

Failure to disable contacts

As mentioned here , your contacts will be auto disabled by the end date if no next posting is scheduled. However, there may be cases where the update might fail.

Scheduled update failed due to reference in routing rules , rosters or broadcast groups

If a contact is referenced in any routing rule, roster, or broadcast group, the contact cannot be disabled or transferred.

Screenshot of email sent for schedule transfer failing due to duplicated MCR number

How can you resolve this issue?

To troubleshoot this issue , you can:

1. Go to the contact on the Directory page and click on the 'Disable Contact' button.

1. If a contact is still being used in any of the following places, you will see an error message when trying to disable them. As shown in the screenshot below, we will need to remove the contact from all active postings first:

   1. Rosters: Any user with the Department Secretary or Institution Superuser role on Rooster will be able to remove the contact's references from the Roster. Only references starting from today will need to be removed.

      1. From the example below, we can identify that our contact has currently been assigned to the Leave roster in column called 'Leave.'

      2. If you are not able to locate your contact in this month, toggle on to the next few months to ensure you have removed all references of your contact

   2. Routing rule: Any user with the Institution Superuser role on Rooster will be able to remove the contact's references from the Roster.

      1. From the example below, we can identify that our contact has been added to the 'Catchall' rule

   3. Broadcast group: Any user with the Message Broadcast role on Rooster will be able to remove the contact's references from the Broadcast group.

      1. From the example below, we can identify that our contact has been added to 'TJY Contact Group.'

2. After removing the contact from the assignments, this contact should be successfully transferred.