View the below list for bug fixes highlighted in this past month's releases:
26.8.4.0 - Wednesday, August 26, 2026
26.9.1.0 - Wednesday, Sptember 2, 2026
26.9.2.0 - Wednesday, September 9, 2026
26.9.3.0 - Wednesday, September 16, 2026
26.8.4.0
Early returns from leave now clear the meal grid: The Mealtime Attendance Report kept a resident marked as on leave for meals even after they returned early. It now recognizes an early return, reopening meal cells for recording as soon as the actual return is logged.
Recorded meals no longer show as blank: When two staff recorded the same meal for the same resident moments apart, the Mealtime Attendance Report could show it as blank. It now reliably displays the recorded status.
Correct leave destination on every meal: The Mealtime Attendance Report showed a generic "on leave" symbol instead of the resident's actual destination (hospital, home, rehab, etc.). It now checks leave status meal by meal, so the real destination shows consistently across every affected meal.
Transferred and readmitted applicants are accessible right away: After a transfer or readmission, a copied applicant record could land under the wrong company, giving staff a permissions error when opening, evaluating, or discharging them. The record now takes on the correct company, so these residents are fully accessible immediately.
Move-in packet compliance documents can be filled and signed: Families and residents could be blocked from entering text or signing move-in packet compliance documents, with only a generic error. Now a signer with multiple roles can complete every authorized field, editing a sent packet no longer removes a signer's access, and filing problems show a clear status instead of failing silently.
GL export failures are caught, flagged, and retryable: When a GL export file failed to reach a client's SFTP server, ALIS still recorded it as complete, dropping those transactions from future exports while logging success and erroring on resend. Failed transfers are now marked failed and flagged for automatic re-export on the next sync, success is logged only on actual success, and Resend works for file-based messages.
26.9.1.0
Incident Reports generate correctly after a template swap: When a community replaced the template file on an existing Incident Form, generated Incident Reports could come out completely blank because the new file was saved to a location the system didn't check. The form and its file now stay in sync.
Email All Prospects works for large lists: Communities with roughly 1,200 or more prospects couldn't email their full prospect list, and the send failed at the recipient step with no error. Emailing all prospects now completes regardless of list size, and a recipient with an invalid email address is flagged inline on its own row instead of silently blocking the whole batch.
Drug Count page no longer times out at shift change: The Drug Count page could hang and error out when many nurses opened it at once during shift change. It now loads reliably regardless of count history size, its three sections load independently with loading indicators instead of failing together, and the Person 2 staff picker is cached for faster loading.
26.9.2.0
Improved Email Validation for Bulk Sending: Fixed an issue that prevented bulk emails (such as invoices and statements) from sending if a recipient's email address ended with more than four characters (like .design or .solutions). These addresses are now correctly accepted so your batches send seamlessly. This improvement also applies to the Bulk Add/Edit Staff page and admin contact fields, and accidental spaces before or after an email address will no longer trigger an error.
Reliable Medication Scheduling After Time Frame Updates: Fixed an issue where updating Med Pass time frames could stall at larger communities, causing scheduled medications to temporarily disappear from the Pass Meds screen. The system now processes these schedule updates quickly and will automatically retry if interrupted. Using the Retry Med Pass Scheduling button will now successfully restore the current day's schedules, including the active shift, without duplicating any medications that were already given.
Incident report tasks display again: Tasks on an incident report were not populating on new or existing incidents. Incident tasks now display on the incident page again. (Shipped in 26.9.2.3)
Care Plan PDFs generate for residents with large care plans: A Care Plan PDF for a resident with many care items and long instructions could spin and then fail, from both the resident profile and the Print Center, and a single resident could cause a community's entire Print Center batch to fail. Care Plan PDFs now generate reliably, and one large plan no longer holds up a community-wide print. (Shipped in 26.9.2.4)
26.9.3.0
Resident Leaves export completes on large pulls: The Resident Leaves export could fail with an error when pulling a large, multi-community date range. It now requests only the data it needs and has more time to finish, so large pulls complete. The export's fields and options are unchanged, so it picks up automatically. Very large pulls may still need a narrower date range.
NJHIN documents are no longer rejected as duplicates: Clinical documents (CCDs) sent to NJHIN all shared the same identifier, so NJHIN rejected them as duplicates even though the send looked successful in ALIS. Each document now sends with its own unique identifier and is stored as a distinct record. This applies automatically; documents NJHIN rejected before this release are not resent. Experiences and the
CRM Dashboard open in training communities: The Salesperson, Caregiver, and Nurse Experiences and the CRM Dashboard appeared enabled in a training community but sent the user back to the home dashboard, and the training community was missing from the community picker on those pages. All four now open correctly in a training community and list it in the picker.