RPT Error Message Glossary
This guide provides a description of error codes and messages that may occur in Interfolio's Review, Promotion & Tenure (RPT).
RPT Error Messages
| Error Message | Explanation of Message | Fix |
|---|---|---|
| Validation Failed: Committee Sorry! You can only add a standing committee to a packet if it is in the packet's unit hierarchy |
The Standing Committee is not in the same Unit as the case or template being edited or created. Therefore, the Standing Committee cannot be added to the case or template. ExampleAn admin is preparing to edit a case template that belongs to The College of Arts & Sciences. They are trying to add a Standing Committee that is housed under The College of Science, but encounter this error message. They must edit the Standing Committee to be housed under The College of Arts & Sciences in order to add them to the case template OR create a new Standing Committee within the unit and add in the respective evaluators/committee managers.
|
The user must edit the Standing Committee to be housed in the respective Unit the template or case is hosted under through the Users & Groups page. Alternatively, if they do not want to modify the existing Standing Committee to belong to another unit, they can create a new one specific to the unit the case/case template belongs to with the respective evaluators/committee managers. |
| Validation failed: Committee is not part of the workflow process | The template they're trying to use has a committee added to a review step in a different unit that they can't use (separate unit). | Go into the template they're selecting and look at each review step's committee to determine which committee is attached that's from a different unit and let them know which one it is that will need to be removed/replaced. |
| Validation failed: Due date Sorry! Due date must be the current date or later | Trying to a set a due date to a date in the past. | Set the due date to the present or future date. |
| Validation failed: Packet type Sorry! The field 'Packet type' can't be blank. | Attempting to save changes on the 'Candidate Requirements' page of an RPT template without a packet type. | Update the template with a packet type, then make changes. |
| Sorry! A valid Committee Member ID must be provided. | Attempting to omit a requirement for a temporary committee member. | To move the case to the next step, delete the temporary committee members from the current review step, then move the case forward. Once the case is on the next step, you can re-add those temporary members to the previous review step. |
| Oops! A server error has occurred. Sorry. |
|
|
| "Internal Server Error" downloading User List | When attempting to download an exceptionally large user list from the "Users and Groups" page, some clients may experience an "Internal Server Error" message. The request (to download the full user list) is timing out due to the size of the database query. Essentially - the list is very large, and the system times out attempting to pull the report. |
|
| {"errors":[{"field":"persistent_id","message":"has already been taken"}]} | When adding an SSO identifier to a user through the User & Groups page, if the user has a duplicate account, you may receive this error message. It refers to the "persistent_id" which is a special key, unique to each user, defined by the institution's SSO configuration. Persistent ID should match SSO ID. When trying to add an SSO ID to a user, it will check the SSO ID against the institution's SSO config. If it detects that the SSO ID being added is already being used as a persistent ID for a user in the SSO config, it means that the user has another account under a different email that is already using that SSO ID/persistent ID. | Merging the two accounts should resolve the issue and merge the two accounts under the same SSO ID / Persistent ID. Be sure to set the correct primary email. |