FAQs: OOO/OOS Data Sync Limitation (Opera Hosted Integration)

🛑 Summary of the Limitation

For properties utilizing an Opera Hosted Integration, there is a technical limitation regarding the depth of OOO/OOS room data transmitted to Optii. When a room status is changed to Out of Order or Out of Service, Opera Hosted does not send the specific OOO/OOS reasons or the scheduled end dates to Optii.

General Information

Q: If the reason and end date aren't sent, what does Optii receive? A: Optii will successfully receive the basic status trigger that a room has been placed into an OOO or OOS state. However, because the end date and specific reason code are missing from the Opera Hosted payload, Optii cannot automatically determine how long the block is supposed to last or why it was put in place.

Q: How often does Optii look for OOO/OOS updates from Opera Hosted? A: Optii performs a full resync of all OOO/OOS statuses every two hours. This automated cycle ensures that any status additions or updates are regularly captured and reconciled throughout the day.

Q: How does this affect our automated Job Scheduling rules? A: Because Optii does not know the end date of the OOO/OOS period under this specific integration, automation rules that rely on duration or specific calendar days (such as "Schedule Departure clean job on the last day" or "Recurring Departure every X days") will not have an end anchor or duration context to work with.

Q: Is there any impact if our property uses Opera On-Premise or Opera Cloud (OHIP)? A: None at all. This is a data-payload limitation unique strictly to the Opera Hosted delivery mechanism. Both standard Opera On-Premise and Opera Cloud (OHIP) work perfectly and sync all data fields.