In plain words
The calendar colours compare each night's room revenue per room with your own other nights, so a busy night can be red, and every day is amber when there are fewer than 10 nights to compare. The calendar, the price box, the Rate Simulator and the change log use your currency's symbol. The change log opens on the 10 most recent runs that changed a price, with Older at the bottom for the ones before, back through 90 days, and 40 changes per run, in your browser's time zone, and hides quiet runs unless you press Show All Cycles.
Why is every day amber?
Colours need something to compare with. Each night's room revenue, from the room types ticked as rooms and any still tagged "needs your answer", is divided by the rooms you could sell that night to give revenue per room (), and past nights are ranked against your other past nights, future nights against your other future nights. With fewer than 10 nights on a side, MAYA borrows both sides together, and with fewer than 10 in total there is no scale and every night is amber. A new property, or a property whose history is still importing, is amber until it has enough nights. The ? under the colour key on the left of the calendar says the same: each night's revenue per room, compared with this property's own nights.
Why is a busy night red?
Because the colour is revenue per room, not occupancy. A full night at low rates can earn less per room than a half-full night at high rates. Red is the bottom third of your nights, amber the middle third, green the top third, each side (past, future) ranked on its own. A property that reversed its colours in Settings sees green for the bottom third and red for the top. The colour tells you how the night's revenue ranks against your own nights, and nothing else.
Why did the colour not change after a booking?
The booked counts and revenue on the visible month are always fresh, but the ranking they are coloured against is kept for up to 5 minutes. A colour can lag a new booking by that long. The calendar also refreshes itself every 5 minutes on the Calendar tab while the browser tab is showing, and when you return to the browser tab.
Why does the calendar show $ when my currency is euro?
The calendar shows the sign of the currency saved for your property: $ for US dollars, € for euros, £ for pounds, and the three-letter code in front of the amount for any other currency. So do the box and its Manual badge, the Rate Simulator, the change log (each change's sentences and prices), a rule's fire log, the Price Change column on the Rules tab, the rule builder's fixed amount box (Adjust by fixed amount (€) in euros), the amounts in Import from PIE, the amber alert banner and the manual price error messages. If the calendar shows $ and your property is in euros, MAYA has US dollars saved for it. That is what a property gets when its currency was not read from its system when it connected. Check Time zone and currency on the PMS tab, and email us to correct it.
Your currency comes from your property system when you connect and cannot be changed in the app.
Why does ADR show a dash when nothing is booked?
The room type card's (average daily rate: that night's room revenue divided by the rooms booked) needs at least one booking. When Booked reads 0 there is nothing to average, so the line reads "ADR –". A calendar day showing ADR, when your property picked it in Settings, shows a dash the same way on a night with no room booked: "ADR –" on a small line, and a dash alone as the big number. Look at Current price for the price your rules have set.
Why are there no weekday headers?
The month grid has none. Click a day and its heading names the weekday: "Friday, November 13, 2026". The grid starts on Sunday.
Why do past months show zeros?
Nights before your property's imported history have nothing to show. The year picker runs from the first month with a booking or a price to the last.
Why does the calendar say "Couldn't load this month"?
MAYA could not read that month just now: its bookings, prices, room types or . A month missing any of them would show nights emptier or cheaper than they are, so it isn't shown at all, and the days of another month or property are never shown in its place. Press Try again. If it keeps happening, reload the page, and if that doesn't help, contact us.
Why are there so many "Prices checked" entries?
Pressing Show All Cycles adds the quiet lines, and a run happens about every five minutes whenever bookings were read. Each line counts a stretch of runs that changed nothing: "Prices checked 47 times from Sep 24, 10:05 AM to 1:55 PM, nothing needed to change." That is MAYA checking your rules and finding no reason to act. Press Show Changes Only to go back to the default view, which keeps only runs that changed something, sending problems and your answers.
Why is the change log empty?
- Nothing has changed yet. The default view hides the quiet lines. Press Show All Cycles to see them. A new property with rules that have not fired shows only quiet lines.
- No run has happened yet. A property that connected minutes ago runs its first cycle within about five minutes.
- The subscription lapsed. A red banner reads "MAYA has paused work on this property". No runs happen until it is fixed.
- Reads are failing. A run whose booking read failed prices nothing and writes nothing. Check Health (last 24 hours) and Last sync on the PMS tab, and look for the connection banner.
- It could not load. "Couldn't load your price history." with a Try again link means the page could not fetch the log. Press Try again.
Simulation is not a reason: while simulating, every run happens and is written down.
Why did an older change disappear?
The change log opens on the 10 most recent runs that changed a price, with the quiet runs between them counted into lines. An older run moves down as new changes arrive, so on a busy day a change from this morning may already be below the newest 10. Click Older at the bottom to add the 10 runs before them, as many times as you need.
A sending problem that is still going on stays at the top of the log until it ends, however long ago it started. Once it has ended, it shows where it ended, among the runs that cover that time, so it may be on an older page. Your answers to the amber banner work the same way.
For one night and room type, Why this price? on its day card lists that night's changes alone, newest first.
Runs, and the detail behind every change, are kept for 90 days, and the log ends there with "Nothing older. History is kept for 90 days." For a change older than that, check the night's Current price and any Manual badge on the calendar. Within the 90 days, if you cannot find a change, email us the night and room type and we can read it for you.
Why are only some of a run's changes listed?
A run lists its 40 biggest changes, largest percentage first, each one a night changed one way across the room types it moved. A run that made more changes than that shows 40, then a line counting the rest, such as "And 23 more changes in this run." ("And 23 more prices would have changed in this run." for a run made in simulation). In a very large run the count can be a minimum: "And at least 23 more changes in this run." The rest are not in the change log. To see one, open the night's Why this price? on the Calendar tab, which lists that night's changes for one room type.
Why is "Show the numbers" missing on some changes?
The button usually appears under a change when a reading for that night goes under it. A booking speed rule that measures the whole property is usually read on each night it could act on, and that reading usually goes under every room type's change on the night. So with such a rule on, the button shows under most changes, including ones made by a (a rule with no booking speed or condition), a price you typed, or a rate changed in your system.
Under those changes the reading is background, not the reason the price moved. The sentence under the change names what moved it. The button shows how the night was booking at the time of that run.
The button is usually missing when no booking speed reading for the night goes under that change, for example when none of the rules you have switched on uses booking speed. A line that covers several room types reads the reading from one of them, so it can show or miss the button where another of those room types would differ. When the reading shows has more.
Whose time zone are the log times in?
Your browser's. " · Fri, Sep 18, 2026, 3:05 PM PDT" is the time on your computer's clock, with its zone abbreviation. Hover the time for the exact moment, to the second, on the same clock. Last sync and the request times on the PMS tab use your clock too. Pricing itself works in your property's own time zone, and the "Updated 3:05:12 PM · live" time on the calendar is also your browser's clock. A rule's fire log shows your property's time instead, with its zone: "Oct 3, 2:05 PM EDT" there is the clock at the property. Why this price? (the time under its price line) and Why didn't it fire? also use your property's clock, with no zone shown, while the changes listed in Why this price? show your browser's clock as the log does.
Why does the PMS tab say "Not tracked for this system" on ThinkReservations or Mews?
The Health (last 24 hours) card and the Recent requests table are filled from a log of MAYA's requests, and MAYA keeps that log for Cloudbeds only. On a ThinkReservations or Mews property both read "Not tracked for this system", however healthy the connection is. Use Connection and Last sync on those properties instead.
The alert banner is out of date
The amber Rules that keep adjusting banner loads when the page opens and when you switch property, and not on a timer. A night you answered in another tab, or a night that has since passed, stays on screen until you reload the page.
The billing, connection and review banners load the same way: when the page opens and when you switch property. A banner for the property you left goes as soon as you switch. Reload the page to see a change made since.
Switching property did nothing
If the switch fails, a short red line under the Property dropdown says so, such as "Couldn't switch to Sea View Inn. You're still on The Harbour Inn. Try again in a moment.", and the property you had stays open. Try again, and reload the page if it keeps failing. Only properties that are paid for and set up appear in the Property dropdown: a property you set aside with "Not now" is listed under Properties not set up yet on the billing page, where Set up brings it back.