# Resolving Rooster's Automated task failures ### 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.

Failure due to missing end date of current posting

If the **end date** of the **current posting** is missing, the contact transfer will fail. {% hint style="warning" %} We display a **warning message** when the end date of the current posting is missing. {% endhint %} 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.

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

#### **Resolving this issue** 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 due to a duplicated MCR

If there are **duplicate MCR values** in the **'Current Main Posting'** or **'Next Main Posting'** with an existing contact in the directory, the contact transfer will fail. #### **Resolving this issue** 1. Ensure you are in the right institution as mentioned in the header of the alert email.

2. Search for the contact by name or MCR number as displayed in the email (e.g ayushi, M12335X) on the **'Directory'** page on Rooster. 3. Click on **'Next Postings'** to modify the MCR number which was causing the issue. Click **'Save'** after modifying the details. 4. Ensure this MCR number is not duplicated by searching for it in the Directory page. 5. If no further errors arise, this contact will be transferred accordingly **the next day**. {% hint style="info" %} If you find that another contact with a MCR number same as the one in your next main posting already exist. Simply remove your next main posting to resolve this error. {% endhint %}

Failure due to start date being earlier than end date

If the **start date** for the next posting is **earlier than the end date** of the current posting the contact transfer will fail. {% hint style="warning" %} We display a **warning message** when users select a start date for the next posting earlier than the end date of the current posting. {% endhint %}

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

#### **Resolving this issue** Users can **wait** until the **end date of the current posting**. The contact will be **automatically transferred** to the next institution. Alternatively: 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 the start date of the next posting is later than the end date of the current posting. 3. Click on '**Save**' after modifying your details. 4. If no further errors arise, this contact will be transferred accordingly **the next day.**

### Failed disablement of contacts When a contact **reaches the end date** of their current posting, the contact should be **disabled** if there is **no next main posting.** However, disablement can fail due to the following:

Failure 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.

#### **Resolving this issue** 1. Go to the contact on the Directory page and click on the **'Disable Contact'** button.

2. If a contact is still being used in any routing rule, roster or broadcast group, you will see an **error message** when trying to disable them. 3. You will need to remove the contact from **all active postings**: 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**. 2. **Routing rule:** Any user with the Institution Superuser role on Rooster will be able to remove the contact's references from the Roster. 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. {% hint style="info" %} 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 {% endhint %} 4. After removing the contact from the assignments, this contact should be automatically disabled.

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://guide.rooster.gov.sg/features/directory-contacts/resolving-roosters-automated-task-failures.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.