Monthly Update Exception Handling
If the monthly update process encounters exceptions, then the application sends a notification that you must resolve exceptions before completing the process.
If the Monthly Update Process page is not already open, then selecting the link in the Exceptions Encountered notification returns you to the page where the application shows the number of exceptions encountered. You cannot proceed with the monthly update until all the exceptions are resolved.
The Cancel option returns you to the initial state. The View Exceptions option opens the Exceptions Summary page where you can examine and resolve the listed issues.
When all the exceptions have a resolution, the application returns you to the Monthly Update Process page where you can restart the process.
When the monthly update is restarted, the process returns to the In Progress stage. Depending on the previous errors and how they were resolved, it is possible to encounter exceptions multiple times. For example:
- When the Apply Previous Value resolution method is used, there may not be a previous value in the affected field for some records. In other cases, the previous value may no longer be valid, such as when a record's next payment date is in the past.
- An exception can occur if one field depends on another field. Initially, a record can show a missing maturity date exception but no error for the next payment date. If the missing maturity date exception is resolved by assigning a maturity date that is prior to the next payment date, then the next payment date fails the next validation since it is now invalid.
When no more exceptions are encountered, the process moves to the Calculations stage to complete the update. Progress messages continue to show as the process moves through the post-update steps.