Resolving Rooster's Automated task failures
This guide will talk about resolving Rooster's automated tasks failures
Last updated
Was this helpful?
This guide will talk about resolving Rooster's automated tasks failures
Last updated
Was this helpful?
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.
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:
Ensure you are in the right institution as mentioned in the header of the email.
Search for the contact by name or MCR number as displayed in the email (e.g ayushi, M12335X) on the 'Directory' page on Rooster.
Click on 'Next Postings' to modify the MCR number which was causing the issue. Click 'Save' after modifying the details.
Ensure this MCR number is not duplicated by searching for it in the Directory page.
If no further errors arise, this contact will be transferred accordingly the next day.
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.
How can you resolve this issue?
To troubleshoot this issue , you can:
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.
Click on 'Next Posting' and ensure your start date is later than your end date date. Click on 'Save' after modifying your details.
If no further errors arise, this contact will be transferred accordingly the next day.
If a contact is being transferred from one institution to another, an end date is mandatory. While we display a warning message to warn you, you will also receive an email notification once the transfer fails.
How can you resolve this issue?
To troubleshoot this issue , you can:
Search for the contact by name or MCR number as displayed in the email (e.g ayushi, M19245X) on the 'Directory' page on Rooster.
Click on 'Next Posting' and ensure your current posting has an end date. Click on 'Save' after modifying your details.
If no further errors arise, this contact will be transferred accordingly the next day.
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.
If a contact is referenced in any routing rule, roster, or broadcast group, the contact cannot be disabled or transferred.
How can you resolve this issue?
To troubleshoot this issue , you can:
Go to the contact on the Directory page and click on the 'Disable Contact' button.
A popup should appear indicated which routing rule or rosters or broadcast group is this contact currently active in
Referenced in rosters: Contact the department secretary in charge of the mentioned roster to remove the assignee accordingly.
Referenced in routing rules: Contact the superuser of your institution to remove the referenced contact.
Referenced in broadcast groups: Contact the users responsible for triggering broadcast groups (typically contact center users in most organisations) to remove the referenced contact.
After removing the contact from the assignments, this contact should be successfully transferred.
