9.7.1 and 9.7.2 Bug Fixes

View the below list for bug fixes included with our 9.7.1 Release on Monday, October 20th, 2025 and our 9.7.2 Release on Wednesday, October 29th, 2025.

9.7.1 Fixes

• Disabled Medication Exceptions not visible despite "Show Disable" toggle on - Disabled Medication Exceptions were not appearing even when the "Show Disabled" toggle was turned on. Now, the disabled exception reasons are visible when the toggle is on. 

• Disabled Classifications showing for active communities - Disabled classifications that existed for previously migrated communities were still showing for active communities in the Historical Census Report under the Classifications tab. Disabled Classifications are now filtered out of the report. 

• Recorded Care Report displaying incorrect communities when printed or exported - When printing or exporting to Excel, the Recorded Care Report displayed incorrect communities that were not included in the Community filter prior to download/export. The printed PDF and Excel export now only show the community or communities that the report was filtered for. 

• Mealtime Attendance ‘Not Present’ displaying as ‘Refused’ in mobile view - When using Mealtime Attendance in mobile view, the ‘Not Present’ option for a resident’s attendance displayed as ‘Refused’. The recording option names are now between desktop and mobile views. 

• Multiple active Resident Monitoring events at once causing incorrect event to be ended when ‘End Monitoring’ action taken - When a resident had multiple active Resident Monitoring events occurring simultaneously, it caused an error with the ‘End Monitoring’ workflow. When the community would ‘End Monitoring’ for a specific event, a different event would be ended instead. Now when ending one monitoring event while others are still active for the same resident, the correct event is ended.

• CRM Dashboard page showing incorrect ‘Current Occupancy’ data - The CRM Dashboard was showing a ‘Current Occupancy’ that did not match the data from the Unit Occupancy report and the “Prospects - New” HQ report. The Current Occupancy value was updated on the CRM Dashboard to reflect accurate data. The CRM Dashboard now excludes secondary residents and shows the current occupancy instead of the projected end of month occupancy. 

• ALIS Pay ‘Customer ID is invalid’ error for one-time payment methods - When ALIS Pay payers utilized one-time payments, the payment methods were still getting saved to the payer profile, and sometimes even as default payment methods. For companies using iStream, one-time payment methods were failing with the response of "Customer ID is invalid" when used again. Now, one-time payment methods are disabled after they are used, and iStream one-time payment methods successfully pull through the payment gateway without error. 

• Disabled Prospect Sources still showing - Disabled Prospect Sources were still showing up as options to select from the dropdown when adding new Prospects. If a Prospect Source is disabled, it is no longer visible or available to select when adding a new Prospect. 

• Recorded Care EP timing out - The first version of the recorded care endpoint was timing out due to a high volume of data being pulled back. The query was improved to be more efficient and now has an added community ID filter. The endpoint will now timeout less, and data can be pulled back at the community level to reduce volume.

9.7.2 Fixes

• Resident Dropdown Performance Issues in Reports - The recently updated billing reports with multi-select community filters caused performance issues with the resident dropdowns on some reports. Now, resident dropdowns are performant regardless of how many communities are selected.
• Check Scanning updates - Check scan deposits were failing due to issues with the MICR. Added a “Done Reviewing” button to the check review process. Rebuilt the check scanning workflow to be more user friendly and the data submission to iStream to be more reliable.
• Fix rounding on Residency Agreements - Rounding preferences in bulk and single generated residency agreements were using the preferences that were set when the agreement was generated and not what is currently set. Now, the rounding setting is only "locking" after verifying the new rate until that rate is implemented. Otherwise, the rounding setting is respected.
• Bulk Primary Payer endpoint 258 errors - Network timeout errors were occurring intermittently for this Sunbound endpoint. An update was made to data types being used to make the query more efficient.