Known issues
Please see the OCLC System Status Dashboard for active issues.
Current issues
Issue | Details |
---|---|
Multilingual circulation groups cannot configure notification policies Notification policies display and are saved incorrectly in OCLC Service Configuration when configuring translations to support multiple languages across the group.
|
Identified: July 2024 |
Circulation groups cannot place item-level holds for items held by other institutions Library staff cannot place item-level holds for items that are held by any other institution in the group, regardless of library policy. |
Identified: July 2024 Workaround: If possible, create an title-level hold with the location of the item selected as the fulfillment location. This workaround will not work if a patron needs a specific volume or issue, etc. |
Undefined normal hours cause special hours to be ignored If normal hours are not fully configured for an institution or branch, then any special hours will not be honored when calculating due dates, overdue penalties, etc. |
Identified: July 2024 Workaround: Update your open hours in the WorldCat Registry to set normal hours of operation for each day of the week. See Open Hours for details. |
List of claimed loans is sometimes incorrect for a patron's account If multiple loans were claimed at exactly the same time, then all of the claimed loans will display the same title, barcode, etc., in the patron Claims tab in the staff interface. |
Identified: July 2024 |
Loans failed to automatically renew on 17 July 2024 A system outage on 17 July 2024 caused some loans to fail to automatically renew. Your institution may have been impacted if your overdue notifications and automatic renewal processing occur between 01:00 - 03:00 U.S. Eastern Daylight Time. |
Identified: July 2024 Workaround: Use the bulk renewal client to proactively renew the impacted loans. This will restart the automatic renewal cycle on the new due date. Criteria for impacted items would be:
Caution: To avoid overdue penalties from being raised by the renewals, you may wish to adjust your loan policies while the client is processing the renewals to either:
|
POS Printer Server Application does not run from the Start Menu on Java versions later than Java 8u162 Later versions of Java 8 introduced a bug which will fail to launch applications from the Start Menu of your workstation. Note: Java 9 and higher are not yet supported. |
Identified: May 2018 Workaround: Install Java SE Runtime Environment 8u162 or earlier to run the POS printer application from your workstation's Start Menu. If you must run a later version of Java 8, you can still run the applications by executing the JNLP files directly (i.e. wms-posprinter-server.jnlp). |
Fixed issues