In plain words
MAYA reads your bookings about every five minutes, your own rates about once an hour (Cloudbeds and ThinkReservations), and the whole once a day. A new booking, a cancellation, a date change or a room move shows in MAYA on the next read. A rate you change in your system is read within the hour. Blocked rooms, allotments and restrictions are not read at all. Your property's name is read once, when you connect. On Cloudbeds the time zone and currency are checked again once a day; on ThinkReservations they are read once, when you connect; on Mews we set them with you.
Three clocks set how soon a change in your system reaches MAYA. This page names them, then lists every change you can make and which clock it rides on. Where a system is different, its tab says so.
The three clocks
| Clock | What is read | How often |
|---|---|---|
| The cycle | Bookings made or changed since the last read, and your room types | About every five minutes |
| The rates read | Your own nightly rate on the plan, for tonight and the next 395 nights, and your rate plans | About once an hour, or when your changes (Cloudbeds and ThinkReservations only) |
| The daily re-read | Every booking in the window, 30 days back and about 13 months ahead | Once a day |
"Next read" below means the next cycle, up to about five minutes on a healthy connection. "Within the hour" means the next rates read.
Every change, and when MAYA picks it up
| You do this in Cloudbeds | MAYA picks it up |
|---|---|
| Make a booking | Next read. A booking waiting in the unassigned list counts too |
| Cancel a booking, or mark it no-show | Next read. Its nights come off the count |
| Take a room off a booking that holds several, or cancel one of its rooms | Next read. That room's nights come off the count. The booking's other rooms stay as they were |
| Add a room to a booking | Next read. The new room is counted. The rooms already counted are not counted again, and the booking is still one booking for |
| Delete a booking | If Cloudbeds still returns it marked as deleted, every night of it comes off the count at the first read that returns it, the daily re-read at the latest. If Cloudbeds no longer returns it, at the daily re-read, so up to a day later: MAYA asks Cloudbeds for it by its number. Once Cloudbeds answers in so many words that it has no such booking, its nights from today on come off the count, and nights already past stay in your history. If Cloudbeds answers that it is cancelled or deleted, every night of it comes off. Any other answer, or a re-read that returned no bookings at all, leaves the booking as it is until the next re-read |
| Change a booking's dates | Next read. New nights are added and dropped nights removed |
| A guest checks out early (stay shortened) | Next read, once Cloudbeds shows the shorter stay. The nights it no longer covers count as free rooms again. If the booking still shows the old check-out date, MAYA still counts those nights as booked |
| Move a booking to another room type | Next read. The room's row gets the new room type |
| Confirm a Confirmation Pending booking | Nothing changes. Both count as booked |
| Change a rate on a night MAYA has never sent to | Within the hour, and always before MAYA's first send to that night. Your rate becomes the night's starting point |
| Change a rate on a night MAYA has sent to and confirmed | Within the hour, once MAYA's send is at least 60 minutes old. Kept as "Changed in Cloudbeds", or with MAYA's price wins on, sent over with MAYA's price |
| Remove a rate on a night MAYA has sent to and confirmed | Within the hour, the same way. MAYA stops pricing the night until Cloudbeds has a rate again, or with MAYA's price wins on, sends its price there again |
| Change most nights MAYA has sent to by the same percentage (80% or more of them, and 10 at least) | Not kept as yours. It reads as a markup in your system, and MAYA's next price replaces them. Type those prices in MAYA instead |
| Set a night's rate to 0 (close it) | Within the hour. Your rules leave the night alone unless a price is typed for it in MAYA. So also clear any price you typed for that night in MAYA. Otherwise MAYA may keep your typed price and send it once you are live |
| Rename, rebuild or delete a rate plan | Within the hour, at the next rates read, or sooner if a send to the old plan fails. MAYA then sends to the new |
| Add a room type | Next read, ticked as a room. Untick Counts as a room on the PMS tab if nobody sleeps there. Set its floor and ceiling |
| Remove a room type | At the next full read, once a day. MAYA switches it off: it is no longer priced and its units leave occupancy and your bill, and the change log says "Deluxe is no longer in Cloudbeds." Nothing is deleted; its past stays remain. Until then its prices cannot be sent. If it comes back in Cloudbeds, it comes back on in MAYA at the next read |
| Change a room type's number of units | Next read |
| Block a room, mark it out of order, or hold an allotment | Not read. Record it under Rooms out of service in MAYA |
| Change restrictions, minimum stays, closed to arrival | Not read, never written |
| Change taxes and fees | Nothing. Once a day MAYA asks Cloudbeds for them, because Cloudbeds requires it, and keeps and uses none of it |
| Uninstall MAYA | Usually within seconds. Otherwise on the next read |
| Change your Cloudbeds password | It may end the connection. If a banner appears, a General Manager or Hotel Admin reconnects in one click |
| Change the property's time zone | At the next full read, once a day. MAYA follows it, and the change log says "Your time zone changed from America/Denver to America/Chicago, to match Cloudbeds." |
| Change the property's currency | At the next full read, once a day. While you are in simulation MAYA follows it and the change log says so, with nothing converted. Once you are live MAYA keeps the currency it has, and our team is alerted |
| Change the property's name | Not read after connect. Email us |
| You do this in ThinkReservations | MAYA picks it up |
|---|---|
| Make a booking | Next read |
| Cancel a booking, or mark it no-show | Next read. Cancelling changes the booking, so it arrives with everything else. Every room it held comes off the count, one taken off it earlier included |
| Take a room off a booking that holds several, or cancel one of its rooms | Next read. That room's nights come off the count. The booking's other rooms stay as they were |
| Delete a booking | At the daily re-read, so up to a day later, when the re-read finishes in one go. A deleted booking is no longer in what ThinkReservations returns, so MAYA asks ThinkReservations again for the bookings on just that booking's nights. Once that answer comes back without it, its nights from today on come off the count. A booking found again, any other answer, or a re-read that returned no bookings at all, leaves it as it is until the next re-read. Nights already past stay in your history |
| Change a booking's dates | Next read. New nights are added and dropped nights removed |
| A guest checks out early (stay shortened) | Next read, once ThinkReservations shows the shorter stay. The nights it no longer covers count as free rooms again. If the booking still shows the old check-out date, MAYA still counts those nights as booked |
| Move a booking to another room type | Next read |
| Change a rate on a night MAYA has never sent to | Within the hour, and always before MAYA's first send to that night. Your rate becomes the night's starting point |
| Change a rate on a night MAYA has sent to | Within the hour, once MAYA has read its own price back there and the send is at least 60 minutes old. Kept as "Changed in Think Reservations" |
| Change most nights MAYA has sent to by the same percentage (80% or more of them, and 10 at least) | Not kept as yours. It reads as a markup in your system, and MAYA's next price replaces them. Type those prices in MAYA instead |
| Set a night's rate to 0 (close it) | Within the hour. Your rules leave the night alone unless a price is typed for it in MAYA. So also clear any price you typed for that night in MAYA. Otherwise MAYA may keep your typed price and send it once you are live |
| Rename, rebuild or delete a rate type | Within the hour, at the next rates read, or sooner if a send to the old rate type fails. MAYA then sends to the new |
| Add a standard rate type with rates of its own | Within the hour, at the next rates read. It shows under Also moves with MAYA on the PMS tab: ticked while you are in simulation, held out and New once you are live, until you tick it |
| Change a rate on one of your other standard rate types | Within the hour. On a night MAYA never moved it is the rate type's own rate; on a night MAYA moved it, once MAYA's price was read back there, it is kept as that rate type's own rate and later changes stack on it. On one you have unticked it stays yours |
| Add a room type | Next read, with its rooms counted from ThinkReservations' list of rooms. Untick Counts as a room on the PMS tab if nobody sleeps there. Set its floor and ceiling |
| Remove a room type | Next read. It is switched off in MAYA: no longer priced, and its rooms no longer count in occupancy or your bill. Its past stays stay in your history. The change log says so under "Changed in Think Reservations". If it is listed again, it comes back on |
| Add a room, or mark one inactive, not a room or not included in occupancy | Next read. MAYA counts each room type's rooms from ThinkReservations' list of rooms on every read. A booking on a room marked not a room or not included in occupancy is left out of occupancy and . Read How many rooms each room type has |
| Move a room to another Room Group | Next read. Its room type shows under the new group. A rule you saved keeps the room types it has, so it doesn't follow the move. Read Room groups |
| Block a room or mark it out of order | Not read. Record it under Rooms out of service in MAYA |
| Change restrictions or minimum stays | Not read, never written |
| Remove MAYA's access | On the next read that fails. ThinkReservations does not tell MAYA |
| Change your ThinkReservations password | It may end the connection. If a banner appears, a General Manager or Hotel Admin reconnects in one click |
| Change the property's time zone, currency or name | Not read after connect. Email us |
| You do this in Mews | MAYA picks it up |
|---|---|
| Make a reservation, an option, an enquiry or a request | Next read. Every state but Canceled counts |
| Cancel a reservation | Next read. Its nights come off the count. Mews records a no-show as a cancelled reservation, so a no-show comes off too |
| Change a reservation's dates | Next read |
| A guest checks out early (stay shortened) | Next read, once Mews shows the shorter stay. The nights it no longer covers count as free rooms again. If the reservation still shows the old departure date, MAYA still counts those nights as booked |
| Move a reservation to another room category | Next read |
| Confirm an option | Nothing changes. Both count as booked |
| Change a rate | Not read. MAYA does not read Mews rates |
| Add a room category | Next read, with its rooms counted from your spaces |
| Remove a room category | Never removed in MAYA. It keeps its past stays and still counts as a room, with the units of the spaces Mews still lists in it, in occupancy and in your bill, so untick Counts as a room on the PMS tab |
| Add a space, switch one off, or move one to another category | Next read: each category's units follow |
| Block a room or mark it out of order | Not read. Record it under Rooms out of service in MAYA |
| Change restrictions | Not read |
| Revoke the keys | Reads start failing and Last sync stops moving. After three refused reads in a row, about half an hour, Connection reads Error and the "Mews needs its keys re-entered" panel appears, and an hour later your General Managers and Hotel Admins get an email. Email us for new keys |
| Change the property's time zone, currency or name | Not read. Email us |
Three kinds of booking people ask about:
- An extended stay or a date change. The added nights belong to the same booking and keep the date it was first made. They count as booked rooms from the next read, but for booking speed they are an old booking, so they rarely show in Past day or Past week.
- A day-use booking (in and out the same day). It is not skipped. In ThinkReservations and Mews it counts as one night on its date. In Cloudbeds it counts on each date Cloudbeds lists a room rate for, so on its date when Cloudbeds lists one. Either way it reads as a booked room that night.
- A comp, house-use or owner stay at $0. It counts by its status, like any booking: a booked room for occupancy and a booking for booking speed. It adds $0 to the calendar's revenue and lowers the . Read Comp, house-use and day-use bookings.
A test booking, made and then cancelled
A test booking counts like any other booking while it is in your system. What happened depends on whether a read found it before you cancelled it:
- Cancelled before the next read (within about five minutes). The read finds it already cancelled, so it is never counted and no price moves.
- Still there at a read. It counts as a booked room and a new booking on its nights, and your rules run with it on that cycle. The next read after you cancel it takes it off the count.
If your rules ran with it, here is what happens to what they did:
- A standard rule (no booking speed or pickup count condition) follows the count. A change that needed the test booking comes off on the cycle that reads the cancellation, and a change it was holding back can now happen.
- A booking speed or pickup change comes off when its rule's undo box is ticked and the cancellation means the rule is no longer true. One test booking may not be enough, and bookings made since can keep the rule true. A cut made because a night was booking slowly never comes off this way. Read When a price change comes off.
In simulation nothing was sent. If you are live on Cloudbeds or ThinkReservations, a price it moved was sent like any other (nothing is ever sent to Mews). To put a night straight back, type the price you want on the calendar. Read Undo a price change.
To test without moving any price, book a night more than 395 nights ahead and cancel it straight away. Your rules run on tonight and the next 395 nights only.
Things MAYA never reads
From any system: availability by night, room blocks, out-of-order rooms, allotments, restrictions, minimum stays, closed-to-arrival flags and closed-to-departure flags. Guest details that come with a booking are dropped before anything is saved. Your property's name is read once, at connect, and never again. The time zone and currency depend on your system. On Cloudbeds they are checked once a day: MAYA follows a new time zone, and a new currency only while you are in simulation, so a property that connected before its time zone could be read, and started on UTC, is put right by the next daily read. On ThinkReservations they are read once, at connect. On Mews we set them with you. Read what MAYA reads and writes.
When it takes longer
- A large property's first read can take several cycles. Each cycle reads for a fixed slice of time and carries on from where it stopped. Until the whole window has been read, your rules run on what has arrived and nothing is sent.
- A failing connection is tried again 10 minutes later, then about every 15 minutes. Nothing is priced or sent on a cycle where the read failed, so bookings are never priced on stale data.
- If your system keeps asking MAYA to slow down, MAYA waits a minute or two before calling it again, and sends move to a later cycle.
- Nights 396 or more days out (past tonight and the next 395) are neither read for rates nor sent until they enter the window.
- A rate you change within an hour of MAYA's send is not yet kept as yours (or, with MAYA's price wins on, sent over), and MAYA's next price for that night can write over it. Wait an hour after a send before changing that night's rate by hand, or type the price in MAYA instead. Read rates you change in your property system.
Example: A Tuesday at The Harbour Inn on Cloudbeds
At 3:02 PM (US Pacific, the property's clock) a guest books a Standard room for Sat, Nov 14 2026. MAYA's next read, at about 3:06 PM, counts it. At 3:20 PM Priya changes that night's Standard rate in Cloudbeds from $150 to $160. MAYA last sent to that night at 2:10 PM, over an hour earlier, so on the next hourly rates read, by about 4:10 PM, the night shows "Changed in Cloudbeds · $160.00" and is kept. At 4:30 PM the front desk blocks room 204 for a plumber until Friday. MAYA does not see that. Priya records 1 unit of Standard out of service from Tue, Oct 6 2026 to Fri, Oct 9 2026 on the PMS tab, and for those nights is right on the next run.