November 19th 2025

Created by Nuša Prejac, Modified on Wed, 19 Nov at 4:59 PM by Nuša Prejac

Release notes BackEnd Flex version 2.44.0, 2025-11-19

ETA and ETD are not correct on the web

Fixed an issue where estimated arrival and departure times (ETA and ETD) were displaying incorrectly in assignment details on the web, despite being correct in the mobile app. The data sync was corrected so that ETA and ETD now show consistently and accurately across all platforms. This ensures users always see the correct timing information.

OOO removed even though another one valid

Resolved a problem where removing one Out of Order (OOO) status from a room would also remove another active OOO, even if it was still valid. Now, canceling one OOO leaves any other overlapping or still-active OOO statuses in place, preventing rooms from being mistakenly marked as available.

OOO from LL not reflected in Flexkeeping.

Fixed a bug where Out of Order (OOO) statuses set in the property management system (PMS) were not syncing automatically to Flexkeeping, requiring manual updates. Now, when a room is set to OOO in the PMS, this status is correctly reflected in Flexkeeping, reducing manual work for staff.

Bed config incorrectly handled - RMS

Addressed an issue where the system made two updates to bed configuration—one with correct data and another without—causing the setup to be added and then removed daily. Updates now only occur when the correct information is available, preventing unnecessary changes and optimizing the process.

Missing AS for Late Check Out Noon

Fixed a bug where the system did not automatically create a late check-out service for a guest room when required. The process was updated so that whenever a late check-out is set, the automated service is reliably created for the correct room.

OOO status in Flexkeeping is removed without a trigger from LL

Resolved a bug where Out of Order (OOO) status for rooms was being removed automatically after midnight, even without a removal trigger from the external system. Now, the OOO status remains active until the correct trigger is received, preventing unintended removals.

Automated assignments should not be trigered for checked-in reservations if the show in future is "arrival" date

Improved the assignment generator so that automated assignments are now skipped for reservations already in-house when the generator is set to show tasks based on arrival date. This prevents irrelevant tasks from being created for past arrivals, reducing workflow clutter.

Mismatch in data between /space_status and /workday endpoints

The system previously showed inconsistent room status information across different endpoints, causing confusion for staff. This was due to manual status changes not updating all relevant tables, resulting in unsynchronized data between /space_status, /workday, and mobile views. The logic was updated so that any manual status change now correctly updates all related records, ensuring room statuses are always consistent everywhere in the system.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article