Only Checked-Out Rooms Import When Syncing Tasks from PMS (MOP 2.0)
In some cases, properties may notice that when importing tasks from the PMS, only checked-out rooms appear in MOP while other room types (such as stayovers or arrivals) do not. This behavior may indicate an issue with PMS data synchronization or the Reservation API connection.
What Is Happening
When importing tasks from the PMS:
- Only checked-out rooms appear in MOP
- Other room statuses are missing
- No visible errors appear to the user during the import
In some cases, system logs may also show no obvious errors at first glance.
What This Indicates
Task imports rely on successful communication with the PMS Reservation API during syncs.
If MOP is unable to retrieve reservation data:
- Only limited room data (such as checked-out rooms) may be returned
- Other room statuses may not be available for task creation
Any issues calling the Reservation API should be visible in system logs and can help identify the root cause.
Log Review and API Validation
Support teams should:
- Review logs to confirm whether MOP is successfully calling the Reservation API during syncs
- Look for any API-related errors, timeouts, or missing responses
- Verify that reservation data is being returned as expected
Any Reservation API errors should appear in logs and provide additional context.
What You Should Do
For Property Users:
If you notice only checked-out rooms importing:
- Confirm the issue occurs consistently when importing tasks.
- Note when the issue started and whether it ever worked previously.
- Contact Visual Matrix Support and provide:
- Property ID
- Description of the issue
- Approximate date/time of task imports
For Support Teams
- Validate Reservation API calls during PMS syncs
- Confirm expected reservation data is returned
- Compare behavior against other properties using the same PMS
- Determine whether this is isolated to a single property or could impact others
Still Need Help With This Topic?
Ask Yourself:
- Are only checked-out rooms appearing after every import attempt?
- Did this behavior start recently?
- Is this a new property or an existing one?
- Are other properties experiencing the same issue?
Support May Ask You:
- What is the property ID?
- Has task importing ever worked correctly for this site?
- When did the issue first occur?
- What PMS is the property using?
- Do logs show any Reservation API errors or missing responses?
Related Articles
What to Do if MOP Isn’t Syncing Properly (MOP 2.0)
If MOP 2.0 isn’t syncing tasks or room updates, use the quick steps below to resolve common connectivity-related delays. Quick Fixes When MOP Is Not Syncing 1. Refresh your Screen - Swipe down (pull-to-refresh) to reload task and room data. 2. Log ...
Supported PMS Integrations for MOP 2.0
MOP 2.0 is an independent mobile platform that connects to multiple PMS systems through API integration. This article outlines which PMS platforms are supported. How Integration Works MOP 2.0 connects to PMS platforms through APIs, allowing room ...
FAQ - MOP / SynXis Property Hub (SPH) Integration
How does MOP know which rooms need cleaning when using SynXis Property Hub? MOP regularly pulls information from SPH about vacant dirty rooms and in-house reservations. This helps generate cleaning tasks based on the room's current status, such as ...
Housekeeping Task Lifecycle (MOP 2.0)
Housekeeping tasks are a critical part of daily hotel operations, directly impacting room readiness, guest satisfaction, and internal coordination. In MOP 2.0, housekeeping tasks follow a structured lifecycle that provides real-time visibility into ...
Import Room Assignments (SynXis Property Hub/SPH) (MOP 2.0)
When connected with SynXis Property Hub (SPH), the rooms are first assigned to each housekeeper in the PMS and then imported in MOP. Because of the 2way connection between MOP and SPH, if a room is checked out of the PMS or if a room status changes ...