FYRO warning/error/failed/success messages
It was suggested to capture messages generated from FYRO to help other libraries who are new to the process or about to do their next FYRO be better prepared or potentially help ease anxiety 
| FOLIO release you are on | example of warning/error/failed/success messages | Time of your FYRO (month/year) | How was it resolved if applicable or comments/your name | JIRA ticket info if applicable | Notes | |
|---|---|---|---|---|---|---|
| 1 | Nolana | "Rollover poLines by chunks failed" got this error message and rollover failed for both smaller ledgers we did FYRO while rollover tests were successful for both | June 2023 | EBSCO FSE response - this error is connected to performance and infrastructure in Nolana, they are looking to get it fixed soon. Was told they implemented improvements in Orchid to have this resolved already. (Dung-Lan Chen, Skidmore College); Told by EBSCO FSE ... they executed a script to fix encumbrances (there were some encumbrances in unreleased status but should be in released - as a result they couldn't be removed during order rollover and failed). It was fixed!! | Make sure you run FYRO in Chrome if you don't normally use Chrome as the browser!! | |
| 2 | Nolana | "duplicate key value violates unique constraint "transaction_pkey" got this error for our major ledger rollover which also failed | June 2023 | Contacted EBSCO FSE and waiting for response; EBSCO FSE responded they executed a script that did a rollover for order lines that failed for the first try. That script worked and got the error fixed. (Dung-Lan Chen, Skidmore College); | ||
| 3 | Nolana hf1 | "Rollover has completed with errors, Budget close Success, Order rollover Error, Financial rollover Success" 504 Gateway Time-out | June 2023 | Pending (Aaron Neslin, 5C) - Allegedly an architecture issue with Nolana | ||
| 4 | ||||||
| 5 | ||||||
| 6 | ||||||
| 7 | ||||||
| 8 | ||||||
| 9 | ||||||
| 10 | ||||||
| 11 |