Messages you might see, explained

Type a few words of the message to jump to itWhen something looks wrongUpdated October 12, 2026

In plain words

Type a few words of the message into the box below to jump to it. Many of the messages MAYA shows are here, grouped by where you see them, and each group stays closed until you open it or the box finds a match inside. Each entry says what the message means and what, if anything, to do, and some link to a page with more. Where a message names Cloudbeds, the same message names Think Reservations or Mews on those properties. Lines only Why this price? or Why didn't it fire? write aren't listed here, such as the reasons Why didn't it fire? gives: for how those two read, see Why this price? and Why didn't it fire?.

Type a few words of the message

Show the 48 messages

"Sign in to MAYA" and "Create your MAYA account": two modes of the one sign-in card. The links "New to MAYA? Create your account" and "Already have an account? Sign in" switch between them.
"Forgot password?": under the Sign In button. It opens "Reset your password", with "Type the email you sign in with, and we'll send you a link to set a new password." and a Send reset link button. "Remembered it? Sign in" goes back. Reset your password
"Welcome back.": the ordinary sign-in intro.
"Set a password and you're on your way. Your property comes next.": the create-account intro. After the account, you pay, then connect.
"Your Cloudbeds property is connected. Create your account to finish setting it up.": you arrived from the Cloudbeds Marketplace. Create an account, or sign in to attach the property to an account you already have.
"Your Cloudbeds property is connected. Sign in to finish setting it up.": the same, on the sign-in form. Signing in attaches the property to your account.
"2 of your properties use a currency MAYA doesn't price in yet, so they weren't connected." (or "1 of your properties uses…") under one of the lines above: your Cloudbeds login covers a group, and those properties' systems use a currency MAYA doesn't price in yet. The rest connected. Currency
"Your Cloudbeds connection is active again. Sign in to pick up where you left off.": you pressed Connect App in the Marketplace for a property that came through the Marketplace and already has an owner. Sign in; everything is as you left it. (A property connected from inside MAYA lands on its PMS tab with "Reconnected." instead.) Connection lost
"Passwords don't match.": retype both password fields.
"That email already has an account. Sign in instead.": the card has switched to sign-in mode. Account and billing problems
"Invalid login credentials": wrong email or password. Passwords are at least 8 characters. Forgotten it? Click Forgot password?. Account and billing problems
"Check your email" with "A confirmation link is on its way to" your address and "Open it to finish signing up.": your account is made. Open the link in the email and you are signed in. "Your Cloudbeds property is saved and will be waiting." means the Marketplace property is kept for you meanwhile, in that browser, for 24 hours from Connect App. Create an account and sign in
"Confirm your email first. The link is in your inbox.": you signed in before opening the confirmation link. Open it, or click Send the link again for a new one. If the email has not arrived
"Send the link again": sends a new confirmation link. It is greyed out for a minute after each email. Only the newest link works.
"Sent. Check your inbox.": the new confirmation link is on its way.
"Too many emails for now. Wait a minute, then try again.": links were asked for too quickly. Wait until Send the link again is no longer greyed out, then click it.
"Could not send the link. Try again in a moment.": the confirmation email did not go. Click Send the link again once more.
"Your email is confirmed. Sign in to continue.": you opened the confirmation link in a different browser or on another device, so it could not sign you in there. Sign in with your email and password.
"That link has expired or was already used. Try signing in.": a confirmation link works once and only for a while. If you opened it before, you are confirmed, so sign in. If not, signing in offers Send the link again. If the link has expired
"Check your email" with "If name@yourhotel.com has a MAYA account, a link to set a new password is on its way. Open it in this browser. The link works once.": you asked for a reset. The words are the same whether or not the address has an account. No email after a few minutes? Check spam. Reset your password
"Sending...": the reset link, or a new confirmation link, is being asked for. It takes a moment.
"Back to sign in": returns you to the card after either "Check your email" message.
"Set a new password" with "Choose a new password for" your address: the page the reset link opens. Type the new password twice and press Save new password.
"Checking your link…": the reset link is being checked. Wait a moment.
"This link has expired or was already used. If you set your new password already, sign in. If not, ask for a new link.", on the "Set a new password" page: each reset link works once and runs out. Sign in, or ask for a new link. Reset your password
"Open this link in the browser where you asked for it. Or ask for a new link from this one.": the reset link was opened in a different browser or on another device. Open it where you asked for it, or ask again from here.
"We couldn't check this link just now. Reload the page to try again.", on the "Set a new password" or "Set your password" page: the check got no answer. Reload; the link still works.
"That's the password you have now. Choose a different one.": pick a password you do not use today.
"That password is too easy to guess. Choose a different one.": pick a less common password.
"Could not save your new password. Try again, or ask for a new link from the sign-in page.": the new password did not save. Press Save new password again. If it fails again, ask for a new link.
"Your new password is set. Taking you to MAYA…": done. MAYA opens, signed in.
"Could not finish connecting your property.": the Marketplace hand-over failed after sign-in. Go back to the Marketplace and press Connect App again.
"That connection link is not valid.": the hand-over link is broken. Press Connect App in the Marketplace again.
"That connection has already been claimed.": another account owns the property. Ask them to invite you. Account and billing problems
"That connection link has expired. Reconnect the app from the Cloudbeds Marketplace.": the link lasts 24 hours. Press Connect App again.
"Sign in to finish connecting.": sign in first, then the property attaches.
"Before you continue": the Terms of Service have a new version. Tick "I agree to the Terms of Service and acknowledge the Privacy Policy" and press Continue. You are asked once. The Terms checkbox
"Tick the box to agree.": the checkbox is empty.
"The terms have been updated. Reload the page to see them.": a tab was open across a new version. Reload.
"We couldn't save that" (please try again): the acceptance did not save. Press Continue again.
"Set your password": the invitation page. Set a password, tick the box, press Set password & continue.
"Verifying your invite…": the link is being checked. Wait a moment.
"This link has expired or was already used. If you set your password already, sign in. If not, email us for a new link.", on the "Set your password" page: the invitation link works once and runs out. If you already set your password with it, click sign in. If not, click email us, which writes to us from your own email, and we send a new link to the invited address. Inviting and removing people
"Password must be at least 8 characters.": choose a longer one.
"Password set. Redirecting to the app…": done. The dashboard opens.
"Hotel not accessible.": you tried to open a property you are not a member of.
"Couldn't switch to Sea View Inn. You're still on The Harbour Inn. Try again in a moment.": under the Property dropdown, with your properties' names. The switch did not go through and nothing changed. Try again, and reload the page if it keeps failing. Several properties on one account
"Sign Out": ends your session and returns to the sign-in page.

Payment, codes and checkout

Show the 34 messages

"Let's get you set up": the subscribe screen. Type your room count, pick monthly or yearly, and continue. Setting up payment
"The Harbour Inn is connected" (with your property's name) with "Try MAYA free for 7 days. Nothing is charged until the trial ends, and you can cancel any time.": a Cloudbeds Marketplace arrival with the trial. Press Set up payment. Codes and the free trial
"Set up a payment method to start using MAYA.": the same screen without a trial. Press Continue to payment.
"Card details are handled by Stripe. They never touch MAYA.": Stripe hosts the card form.
"How many rooms?" and "A whole number between 1 and 500.": type the number of guest rooms. Over 500 is not sold self-serve; email us.
"save 10%" beside Yearly: from 21 rooms. "pay once a year": 1 to 20 rooms pay 12 months at the monthly rate.
"Your code" with "MAYA is invite-only for now" (you will have been given a code): a code is required for this property system. "Your code (optional)": a code is not required; enter one if you have it.
"Checking…": the code is being checked.
"Enter your code to continue.": the field is empty and a code is required.
"We don't recognize that code" (check it for typos): not a code we issued. Account and billing problems
"That code has been turned off.", "That code has expired.", "That code has already been used the maximum number of times.": the code no longer works. Ask us for a current one.
"This property already used that code.": one redemption per property.
"Too many code attempts. Wait a few minutes and try again.": 20 checks per 10 minutes.
"Your session expired" (sign in again and retry): your sign-in lapsed while the page was open.
"Couldn't check that code" (try again in a moment) and "That code didn't work.": the check failed. Try again.
"Your code's terms changed since it was checked. Check them, then continue.": the payment screen was open over 50 minutes, the code was checked again, and what it grants changed. Read the new lines, then continue.
"Couldn't check your code again. Try again in a moment.": that second check could not be reached. The code still stands. Press the button again.
"14 days free, then your normal rate.", "20% off for your first 3 months." and similar green lines: what a valid code grants.
"This code's 14 free days don't apply to a restart, so it doesn't change your price.": a code that only gives free days, typed while restarting a subscription. A restart is billed when checkout completes. Cancelling, restarting and leaving
"No charge was made" (you left checkout before finishing): you closed Stripe's page. Nothing was taken. Continue when ready.
"This page stays open until" a time, above the pay button on Stripe's page: with a monthly code that discounts a set number of months, and four weeks or more free, the page closes sooner than a day. If Stripe's page says it has expired, go back to maya-rms.com and press Continue to payment again.
"Accept the Terms of Service to continue.": tick the Terms box on the screen that appears, and checkout continues by itself.
"Tell us how many rooms you have" (any number from 1 to 500): the room count is missing.
"This property already has a subscription. Manage it at /account/billing.": one subscription per property. Open Billing.
"Your subscription is on hold. Email us at info@modern-hospitality-solutions.com and we'll get it running again.": the property's subscription is paused in Stripe, so a new one is not started beside it. Email us.
"Your subscription is waiting on a card update. Update your card from billing and the subscription restarts where it left off. If it has been unpaid for more than 30 days, update your card, then email us at info@modern-hospitality-solutions.com and we'll restart it.": the property's subscription is unpaid but still alive in Stripe, so a new one is not started beside it. Save a new card as your default in the billing portal and MAYA moves the subscription onto it and pays the open invoice with it, unless the subscription is on a different card of its own, which MAYA never moves. Moving to another card
"Too many checkout attempts. Wait a few minutes and try again.": 10 checkout starts per 10 minutes.
"That property isn't yours to pay for.": you are not a manager of that property.
"We couldn't start checkout" (please try again in a moment): Stripe could not be reached. Try again.
"Payment received" with "Setting up your account": Stripe has confirmed; MAYA is catching up. It moves on by itself. "Your payment went through, but our side is taking longer than usual to catch up." and "...confirming it here has stalled.": press Check again, or leave and sign in later. You have not been charged twice. Account and billing problems
"Property 2 of 3": a group of Cloudbeds properties is paid for one at a time. Paying for a group
"Not now" (set this property up later): skip this property for now. It appears under Properties not set up yet on the billing page.
"This is the only property left to set up.", "This property is already set up.", "This property is already paid for.", "This property isn't waiting on a Marketplace setup.": "Not now" does not apply to this property.
"Manage billing or cancel": opens Stripe for a property that is paid for but not yet connected. "Cancels at the end of the period": that property is already set to cancel.

Connecting your property system

Show the 30 messages

"Connect your property system": pick Cloudbeds or Think Reservations and press Connect →. Mews shows "Coming soon" and "Not yet available": we connect Mews for you. Which systems work
"Sign in with your Cloudbeds account": you sign in on Cloudbeds' own site, nothing to install.
A MAYA page with a short heading, a sentence or two and a button: connecting or reconnecting stopped, and nothing was changed. The heading says what happened and the sentence what to do. The button goes back to where you started: "Back to setup" while you are setting up a property, "Back to the PMS tab" for a reconnect, "Open MAYA" when MAYA can't tell where you started (such as after Connect App in the Cloudbeds Marketplace), and "Sign in" when you are signed out. "Email us" beside it opens an email to us. The messages below are the ones these pages show. Reconnect and disconnect
"Payment comes first" with "Set up payment, then connect your property system.": the connect step was opened before your payment went through. Press Back to setup, finish paying, then connect. Setting up payment
"Already connected" with "Your property system is connected, so nothing was changed.": a second connect was started after your property was connected, from another tab or a page left open. Nothing was added. Press Back to setup (or Open MAYA once set up) to carry on.
"Cloudbeds needs an access code" with "You paid without a code, and Cloudbeds needs one to connect. Connect the system you signed up with, or email us and we'll sort it out.": the system you chose at checkout needed no code, and this one does. Any code used at checkout counts. A code can't be added after paying, so email us. Codes and the free trial
"We couldn't check your signup" with "Nothing was changed. Try again in a moment.": MAYA could not read your subscription just then. Press Back to setup and connect again in a moment.
"This Cloudbeds login covers 3 properties" (MAYA signs one property up at a time): a group login cannot connect from inside MAYA. Cloudbeds groups connect from the Marketplace; ThinkReservations groups are set up by us. Email us. Add a second property
"We hit a snag connecting your property": the connection did not finish. Read the sentence under it, then press Try again, or Back to setup where trying again would fail the same way. Sentences you may see: "We connected to your account but couldn't read your property details. Try again in a moment.", "Could not create your property. Try again in a moment.", "Could not store your connection securely. Try again in a moment.", "This connection link belongs to a different account. Please sign in and try again.", "Set up payment, then connect your property system.", "We couldn't find your subscription. Start again from setup." Cloudbeds
"Cloudbeds wasn't connected" (or "Cloudbeds wasn't reconnected", on a reconnect) with "MAYA wasn't given access, so nothing was changed. Start again and allow access. If Cloudbeds won't let you, email us.": you chose Deny on your system's sign-in page, or your system refused for you. Start again and allow access. If your login isn't allowed to give access, ask whoever runs your system, or email us.
"Cloudbeds didn't finish connecting" with "Nothing was changed. Try again in a moment, and if it happens again, email us.": your system's sign-in, or MAYA's handover with it straight after, did not finish. Nothing is wrong on your side. Try again in a moment.
"Cloudbeds can't be connected right now" with "Nothing was changed. Email us and we'll sort it out.": MAYA isn't set up to connect your system just now. Email us.
"That sign-in link ran out after 15 minutes. Start again from MAYA.": the sign-in at Cloudbeds or ThinkReservations took longer than 15 minutes, so its link ran out. Nothing is wrong and nothing has changed. Press the button on the page and start again. ThinkReservations
"That sign-in link isn't one MAYA can finish, so nothing was changed. Start again from MAYA.": a sign-in came back without the link MAYA made for it, such as from an old bookmark. Start again from MAYA.
"That link is missing its property" with "Nothing was changed. Start again from MAYA.": a reconnect link without its property. Use the button on the PMS tab.
"You're signed out of MAYA" with "Sign in, then start again from MAYA.": the connect or reconnect link was opened while signed out. Press Sign in, then start again.
"Your property's system uses KRW. MAYA doesn't price in KRW yet, so nothing was set up or imported. Email us and we'll tell you when it does." (with your currency's code), sometimes with "Reply to your receipt and we'll sort out your payment.": for now MAYA works only in dollar, euro and pound style currencies. Nothing about the property was kept. Currency
"Cloudbeds did not report a property for this authorization.", "Cloudbeds didn't say which property this is, so nothing was added. Press Connect App again in a moment." and "MAYA couldn't set up this property, so nothing was added. Press Connect App again in a moment.", under "Cloudbeds wasn't connected": after Connect App in the Marketplace, nothing was added. Press Connect App again for the right property, and email us if it happens again.
"This login is for a different property.": the Cloudbeds login you signed in with does not reach this property, so nothing changed. Reconnect with a Cloudbeds login that reaches the same property. Connection lost
"That Think Reservations login can't reach this property, so nothing was changed. Reconnect with a login for this property.": the ThinkReservations login you signed in with does not reach the hotel this property is connected to. Nothing changed. Sign out of ThinkReservations in this browser, then reconnect and sign in with a login that reaches it. Reconnect and disconnect
"That Think Reservations login can't reach any property, so nothing was changed.": the login you signed in with reaches no hotel at all. Nothing changed. Reconnect with a login for this property.
"This reconnect link was started from a different account. Sign in as the person who started it, or start the reconnect again from MAYA.": a reconnect link finishes only for the person who clicked Reconnect, signed in to MAYA in the same browser. Someone else opened it, or you signed out in between. Nothing changed. Reconnect and disconnect
"That link is from before an update to MAYA. Start the reconnect again from MAYA.": the link was made before MAYA started tying reconnect links to the person who starts them. Nothing changed. Click Reconnect again.
"This Cloudbeds login is for a property that is already connected to another property in MAYA, so nothing was changed." (or "This Think Reservations login ..."): the property this login reaches is already another MAYA property. Ask that property's General Manager for an invitation, or email us. Reconnect and disconnect
"We couldn't check this login just now. Try connecting again in a moment.": MAYA could not check which property the login is for, or whether it is already another MAYA property's, so nothing changed. Try again.
"Cloudbeds didn't answer. Try connecting again in a moment." (or "Think Reservations didn't answer."): your system was unreachable, so nothing changed. Try again.
"MAYA couldn't finish saving the new sign-in. Try again in a moment.", under "Cloudbeds wasn't reconnected": the reconnect stopped while MAYA was saving it. Reconnect again in a moment.
"Reconnect this property from the Cloudbeds Marketplace.": press Connect App there.
"This property is already in MAYA, so nothing new was added." (reconnecting it needs General Manager access or higher on it): you pressed Connect App in the Marketplace for a property someone connected from inside MAYA, while signed out of MAYA or without that role. Nothing changed. Sign in to MAYA as its General Manager or Hotel Admin and click Reconnect Cloudbeds on the PMS tab. Reconnect and disconnect
"Could not check whether this property is already in MAYA. Click Connect App again in a moment.": under "Cloudbeds wasn't connected". Nothing was added. Press Connect App again in a moment.

The strip at the top

Show the 7 messages

"Simulation · MAYA works out prices but sends nothing to Cloudbeds": the slim amber strip, with an amber dot, across the top of every screen while your property simulates, the review screen included (with no Go live there). Your rules run and their prices show, and nothing is sent until a General Manager or Hotel Admin goes live. Simulation mode
"Go live" at the strip's right: shown only to a General Manager or Hotel Admin, on every screen but the review. It opens the go-live confirm for the property named in its title. Going live
"You go live from this strip on your dashboard, once you finish here." behind the ? of the review screen's strip: the review has no Go live. Finish the review and use the strip's button on the dashboard. Going live
"A General Manager or Hotel Admin can switch this property to live." behind the strip's ?, or in the confirm when the switch is refused: your role can't go live. Ask one of them. Going live
"Your rules run as they will live, and their prices show on the calendar and in the change log. Cloudbeds keeps its own rates." and "Go live starts sending on the next cycle, about 5 minutes later. To go back to simulation, email us.": the strip's ?, titled "Simulation".
"MAYA doesn't send prices to Mews yet, so there is nothing to switch on here.": a Mews property's strip has no Go live. Mews
"Live": the small green tag at the top right once the property is live. Hover it for "MAYA sends its prices to Cloudbeds." On a Mews property its ? says "MAYA doesn't send prices to Mews yet, so nothing goes to it, live or not."

The import and the review

Show the 46 messages

"Import paused": the history import stopped after repeated errors and tries again by itself at the time the bar gives, from where it had got to. "We've been told" means an automatic alert reached our team. Nothing to do. The history import
"This is taking longer than it should. We've been told.": under the step on the import's bar, at the top of the review after the step, or beside "Reading your history…": the import or read keeps running into errors and is still trying, and our team has had an automatic alert. Nothing to do. The history import
"Import stopped": the history import stopped before it finished and does not try again by itself. With "We've been told.", our team has had an automatic alert. With "Email us and we'll restart it.", nothing reached us: email us. If your system had refused MAYA's access, reconnecting on the PMS tab picks it up again. The history import
"Your import stopped because your property system is no longer connected.": the connection went away while the import ran. Reconnect on the PMS tab and it carries on from where it stopped. "Your import stopped before it finished." means it was stopped for another reason that is not an error, such as choosing Not now for the property. The history import
"Hold My Hand" and "Let Me Drive": the two paths. The first asks five optional questions and walks you through the review. Hold my hand or let me drive
"A few quick questions · 1 of 5 · all optional" and "Skip the rest →": every question can be skipped. The five questions
"Did we get your property's name right?": whatever you type wins. "That property name is already taken": add your city or neighbourhood.
"Your floor of $200 wasn't saved for Deluxe King: its ceiling is $150, and a floor can't be above the ceiling." or "Your ceiling of $150 wasn't saved for Suite: its floor is $180, and a ceiling can't be below the floor.": every other room type took your answer, and the one named kept its own number. Type another number, or skip the question to leave it that way. The five questions
"Your ceiling price needs to be above your floor price of $80." or "Your floor price needs to be below your ceiling price of $300.": the answer clashes with the other one you gave, so nothing was saved. Type another number or skip the question. The five questions
The blue card ending "Review →": your history has been read and there are findings to look at. Press it. Checking what MAYA found
"First: does this match reality?" and "Recommendations from your data": the two passes of the review screen.
"Is "Meeting Room" actually a room?": confirming takes it out of occupancy and your billed room count. Room types and rooms out of service
"Were you closed ...?" with "Yes, we were closed" / "No, we were open", and "Is your property normally closed ...?" with "Yes, that's our season": confirming keeps that stretch out of comparisons. Dismissed dates are not asked again. Similar nights
"Hid duplicate room type" with "Good call" / "Undo": an empty duplicate was hidden. Press Undo to bring it back. After Good call, email us. Checking what MAYA found
"Hide duplicate room type "Standard"?" with "Hide it" / "Keep it": the same finding on a property that is live, or after Get suggestions from my data. Nothing is hidden until you press Hide it.
"This room type isn't an empty duplicate any more, so it wasn't hidden." and "This room type can't be brought back from here.": since the card was written the type got a booking with a rate, the room type with its name was switched off or has no bookings with a rate, or your property system stopped listing it, so nothing changed and the card stays. Press Keep it (or Good call) to clear it. Checking what MAYA found
"Some "Standard" rates look like typos" (with your room type's name), "Some stays have no rate", "Some old stays reference deleted room types": notes about your history. Nothing to do.
"Finding was already resolved": another tab or a colleague answered that card first. Reload.
"Only a Revenue Manager or above can answer this." on a review card: your role is below Revenue Manager, so the card stays. Ask a Revenue Manager or above to answer it. Roles
"A General Manager or Hotel Admin can answer this." behind the ? of an "Is … actually a room?" card with its buttons greyed out: that card changes the room count you are billed for, so it needs a General Manager or Hotel Admin. The card stays until one of them answers it. "Only a General Manager or above can answer this.": a Revenue Manager's answer to that card reached MAYA some other way and was refused. Roles
"Only a Revenue Manager or above can finish the review." with "Go to my dashboard": Finish, Keep them and Remove them and start with a clean slate need a Revenue Manager or above, so the review is not marked done and the dashboard banner stays. The link opens the dashboard anyway. Checking what MAYA found
"Couldn't finish the review. Try again." or "Your review couldn't be marked as finished. Reload the page and try again.": Finish (or Keep them, or a remove that went through) did not save the review as done, so you are still on the review. Press it again, reloading first for the second one.
"We're counting 3 room types as rooms" (anything here that isn't?): untick anything nobody sleeps in.
"Your floors and ceilings": a floor box and a ceiling box for every room. Type an amount to set or change one, empty the box for no limit ("none"). "Saved" under a line: that box saved. "A floor needs to be below the ceiling of $780.", "A ceiling needs to be above the floor of $150." or "Type an amount between $1 and $99,999.99, or leave the box empty for no floor.": nothing was saved; type another amount. "A Revenue Manager or above can change these.": the boxes are greyed out for your role. "That's a lot of changes at once. Give it a minute and try again.": 120 saves in ten minutes is the limit. "Not saved" beside a box: what it holds isn't saved, because a scroll took you out of it or its save was refused; click in and press Enter. Checking what MAYA found
"While you were here, we built your first pricing rules": your , running in simulation. Your starter rules
"Keep them" and "Remove them and start with a clean slate", under your starter rules: both finish the review and open your dashboard, where you go live. "Either way you go to your dashboard. You go live from there when you're ready." says so; for someone who can't go live, the second sentence says who can. "You removed your starter rules.": the box once none of them is left. Your starter rules
"Remove all 5 starter rules?" with "Remove" and "Cancel": the one question before a clean slate. "Remove 4 starter rules? You changed Warm-date bump, so it stays.": a starter rule you edited is yours and stays. "Your starter rules weren't all removed. Try again.": press Remove again and it removes what is left. "Couldn't read your starter rules. Try again.": nothing changed; press the button again. "Only a Revenue Manager or above can change this.": removing rules needs a Revenue Manager or above. Your starter rules
"✓ Live: your rules are now managing prices": you are live.
"Send The Harbour Inn's prices to Cloudbeds?" (your property's name) with "Go live" / "Not yet": the confirm dialog. "MAYA starts sending its prices for the next 396 nights to Cloudbeds on the next cycle, in about 5 minutes." and "Each price it sends replaces that night's rate in Cloudbeds, and a night is sent again whenever its price changes."
"Going live sends MAYA's prices to Cloudbeds automatically. You're confirming you've reviewed your rules and limits (Terms 3.3).": what your click confirms.
"Sending to Think Reservations isn't on right now. You can go live once it is." (with your system's name) on the strip's ?, or when the switch is refused: sending to your system is switched off on MAYA's side, so Go live waits. Going live
"MAYA couldn't check that sending to Cloudbeds is on. Try again in a few minutes.": Go live waits until MAYA can see the switch is on. Reload in a few minutes. Going live
"Sending to Think Reservations isn't on right now." (hovering the Live tag), and behind its ?, "Sending to Think Reservations isn't on right now, so nothing goes to it. Your prices wait until it is.": you are live, and nothing goes to your system until sending is back on. Sending is on for both systems today, so this shows only if it is switched off. Going live
"12 nights have a rate outside your floor or ceiling; MAYA will move them inside when it sends." in the confirm: on those nights your own rate in your system is under a room type's floor or over its ceiling, and going live sends the floor or ceiling instead. Change or remove a limit on the review to keep your rate. Going live
"This page is for another property. Reload and try again." in the confirm: you switched property in another tab since this page loaded, so nothing changed. Reload and check the name in the title. Going live
"MAYA doesn't send prices to Mews yet, so there is nothing to switch on.": a Mews property can't be taken live from your side. Mews
"Get suggestions from my data": re-reads your history and offers changes you accept one by one. The panel "Here's exactly what happens" explains it. When the read is done the button reads "3 suggestions ready →". Getting suggestions later
"Reading your history…": a read you or a colleague started is running. Leave the tab open or come back later: the button changes by itself when it ends. Getting suggestions later
"Your last read paused" and "Your last read stopped": the last read stopped before it finished. "Paused" means it tries again by itself at the time given. "Stopped" means it will not: with "We've been told." our team has had an automatic alert, and with "Email us and we'll restart it." please email us. "...because your property system is no longer connected" means reconnect, then press the button again. Getting suggestions later
"Not available for Mews yet. MAYA can't read its booking history.": Get suggestions from my data is greyed out on a Mews property, because MAYA does not read Mews history yet. Mews
"You need Revenue Manager access or higher to run this.": ask a Revenue Manager, General Manager or Hotel Admin to press Get suggestions from my data. Roles
"A read was just started. Let that one finish before starting another.": Get suggestions from my data was pressed more than 5 times in 15 minutes on this property. Wait, then press it again. Getting suggestions later
"Tune "Busy nights"?" with "Make that change" / "Leave it as is": changes the rule's occupancy threshold in place. On the Rules tab it goes through the Apply or Skip window: with Apply, nights that no longer meet the new threshold lose the rule's change from the next run; with Skip, they keep it until the rule is true there again. Change a rule
"Remove "Quick pickup"?" with "Remove it" / "Turn it off, keep it" / "Leave it running": remove deletes the rule and undoes its changes; turn off pauses it and keeps them.
"Add a rule: "Warm-date bump"?" with "Add this rule" / "No thanks": adds a rule switched On.
"Set a floor for "Standard"?" and "Set a ceiling for "Standard"?" with "Set it to 80": type your own number or accept. Floors and ceilings

Rules and the rule builder

Show the 62 messages

"Pricing Rules": the Rules tab. Filters "all", "enabled", "disabled". The rule builder
"How rules behave": three short animations (a rule that raises and waits, an occupancy rule with no wait, and a stronger rule covering a weaker one), with "Try the box" to play them with the undo box ticked or unticked.
"+ Add a rule" and "Add Rule": open the builder, and save. Add Rule first opens the window below, and the rule is On once you apply, skip or turn it on.
"Edit", with the builder headed "Edit "Busy nights"", "Save changes" and "Cancel editing": change a saved rule. A new name, or a change to a rule that is Off, saves at once; a change to a rule that is On opens the window below. Change a rule
"Rule name": required.
"Conditions" with "Matches when all of the following are true.": every condition must hold at once. "+ Add condition" adds the next kind; nine at most, one of each (eight on Mews, where rooms left to sell isn't offered yet).
"Sellable occupancy (%)", "Rooms left to sell", "Booking speed (recommended)", "Booked so far vs usual", "Booking window (days to stay)", "Current rate", "Pickup count (advanced)", "Recent bookings, whole property (advanced)", "Average rate booked, ADR (advanced)": the nine things a rule can look at. The rule builder
"Ahead of usual by at least" / "Behind usual by at least", with "about 5 rooms" (or "about 1 room", "under 1 room") under the percent: a booked so far vs usual row, and what its percent is in rooms. Booked so far vs usual
"This condition isn't ready on your property yet.": a rule with booked so far vs usual can't be saved until MAYA's checks on your property read it: after an update reaches your property, from MAYA's next check that prices your nights there, at the latest just after midnight at your property. Until then the builder doesn't offer it. Booked so far vs usual
"Compare" with "Greater than" / "Less than" ("Fewer than" / "More than" for rooms left, "At least" / "Fewer than" for recent bookings, "Below" / "Above" for the current rate and , "Ahead of usual by at least" / "Behind usual by at least" for booked so far vs usual), and "Threshold": strict comparisons, except that At least, Ahead of usual by at least and Behind usual by at least include the number. Greater than 80 means more than 80.
"Speed": Stalled, Much Slower Than Normal, Slower Than Normal, Normal, Faster Than Normal, Much Faster Than Normal, Surging. Booking speed
"Measured over" with "Past day" / "Past week" / "Past month": the window of bookings counted.
"Then waits (advanced)" with "1 day" to "2 weeks", and "(pickup holds it to 3 days)": how long the rule leaves a night alone after acting. A rule with a pickup row and a row waits the longer of their two waits.
"Lookback window" and "Pickup measures" with "Room nights (units)" / "Revenue (currency)": settings. Pickup count
"Rate adjustment", "Direction (required)" with "Increase the rate" / "Decrease the rate", "Adjust by percent (%)", "Adjust by fixed amount ($)": a rule has one amount, so typing in one box greys out the other.
"Apply to room types" with "Select all" / "Clear", and the tag "not a room": which room types the rule measures and changes.
"Change prices on different room types" with "Measure" and "Change": watch one set, price another. Measure one set of room types, change another
"Add at least one condition with a valid operator and threshold.": a threshold is empty or negative.
"Choose whether this rule increases or decreases the rate.": the direction dropdown is blank.
"Enter a percent or a fixed amount.": both amount boxes are empty.
"Enter the percentage as a positive number." and "Enter the amount as a positive number.": the direction dropdown sets increase or decrease, so the amount is always positive. An amount of 0 is refused on save.
"A rule can't lower a price by 100% or more.": a cut of 100% or more, in the rule builder, the Rate Simulator's test rule or an import from PIE. Type a smaller percent. The rule builder
"That's a lot of imports at once. Give it a minute and try again.": more than 10 presses of Add or Try again in an import from PIE, by one person on a property in 10 minutes. Nothing was added by that press. Wait a few minutes and try again. Import your rules from PIE
"Select at least one room type.", "Pick at least one room type to measure.", "Pick at least one room type to change.", "Invalid room types.": fix the room type lists.
"Could not save the rule. Check your connection and try again.": MAYA's answer didn't arrive, so the rule may or may not have saved. Reload the page and look in the rules list before adding it again. "Could not save the rule. Try again in a moment.": the save was refused without a reason it could show.
"This property already has 40 active rules, which is the maximum.": 40 rules are already On. Turn one Off or delete one first. How many rules you can have
"That amount is too big to save.": an amount of 1,000,000 or more reached MAYA. Type a smaller number. "Use a percent or a fixed amount, not both.": both amount boxes had a number.
"Take this change back if cancellations remove the bookings that triggered it": the undo box under the amounts, ticked to start. The undo box
"Counted over" with "Yesterday" to "Last 30 full days": the days a recent bookings row counts. Recent bookings
"Same as the lookback window": a pickup row's wait, to start. How long a pickup rule waits
"Filled in for you": the "?" beside a Booking window (days to stay) Less than 60 row the builder added to a cut on low pickup. Change or remove it as you like. A cut on low pickup, far out
"The rule builder doesn't offer Rooms left to sell on Mews yet, so nothing was filled in.": a link to a rule with rooms left, from a docs page or the rule playground, or Open in rule builder in the Rate Simulator on such a rule, on a Mews property. Build the rule with instead. Rooms left to sell
"The rule builder doesn't offer Rooms left to sell until it can read your property system, so nothing was filled in.": the same, on any property, while MAYA couldn't read which system your property is on. Reload the page to read it again. Rooms left to sell
"Change before importing" with "Use in the import" and "Back to the import": a rule from Import from PIE open in the rule builder. Import your rules from PIE
"Only a Revenue Manager or above can change this.", under the form or under a rule: Viewers cannot add, edit, switch or delete rules. Roles
"Give the rule a name.": the name is only spaces.
"Invalid payload.": the rule arrived with no name, no condition or no amount. Fill in the name, a condition and an amount.
"You don't have access to this property.": your account has no property membership. Ask to be invited.
"This rule changed in another tab. Reload it to edit." with "Reload": the rule's conditions, amount or room types were changed and saved somewhere else after you opened it. Reload fills the builder with it as it is now.
"That rule could not be found.": the rule you were editing was deleted.
"That rule could not be loaded. Try again in a moment.", under a rule: Edit could not read it.
"Try again.", under the form: the rule was probably saved already, by an earlier try whose answer didn't arrive. Reload the page and look in the rules list before you add it again.
"Turn on "Busy nights"?", "Add "Busy nights"?", "Save changes to "Busy nights"?": the window before a rule starts acting, with a small calendar and "41 days will be affected by this rule." (or "1 day"): the days whose prices it will change. "0 prices will be affected by this rule.": nothing would change now. "What the days mean" is its "?". Turning a rule on, Apply or Skip
"Apply price adjustments", "Skip price adjustments", "Cancel": change those days from the next run; switch the rule on but keep those days' prices until the rule stops being true on a day and then becomes true again; or save nothing.
"Turn it on": the one button beside "Cancel" when the window reads "0 prices will be affected by this rule.": switches the rule on. For an edit to a rule that is on, the same button reads "Save changes" and saves it.
"Checking your calendar…": the days are being worked out.
"On 40 nights where the rest of this rule is true, there aren't enough similar nights to compare with yet, so it leaves them alone." and "There aren't enough similar nights to compare with yet, so this rule won't change any night until there are.": a booked so far vs usual rule in the window before it starts acting. Turning a rule on, Apply or Skip
"We weren't able to calculate how many days would be affected by this rule.": the check failed or took too long. Choose "Try again", "Skip price adjustments" (the rule is on and changes no price now: every day it could change is held until it stops being true there and then becomes true again) or "Cancel".
"The window didn't open. Try again.", on an Add this rule or Make that change card from Get suggestions from my data: the rule or your room types could not be read, so the window with the days could not open, and nothing was saved. Click the button again.
"Your bookings changed while this was open, so the days were checked again.": something changed before you clicked Apply, Skip, Turn it on or Save changes, and the days came out different; the new days are shown. Choose again. When they came out the same, the rule is saved with no line.
"Your bookings or prices changed again while this was saving, so nothing was saved. Try again in a minute.", in red in the same window: the days were checked again and something changed again straight after. Nothing was saved. Click your choice again in a minute.
"That's a lot of checks at once. Give it a minute and try again.": too many windows opened in a few minutes. It shows under "We weren't able to calculate…".
"Choose whether to apply the price adjustments.": a rule was about to start acting without an answer from the window, for example a suggestion card clicked before the page had finished loading. Nothing was saved. Click the button again and choose in the window.
"This needs a database update first.": rules can't be saved on your property until we update it, whichever button you pressed. Email us.
"Fired" with "3×" or a dash: how many the rule has acted in over the last 90 days, each run once however many nights and room types it changed, including changes that came off. "What counts as a fire" is its help. Click the number for the rule's fire log. A dash you can click opens Why didn't it fire?; a plain dash means the counts couldn't be read just then, so reload the tab.
"12 fires in the last 90 days" under a rule's name in a window: its fire log, one row per run the rule acted in, with when it fired in your property's time and zone, the nights and room types ("Nov 11 to 12 · 7 room types"), and the adjustment. Click a row for each night and room type with the price before and after, where it went, why and what came later. "Simulation" beside a fire, and "Simulation: these are the prices it would have set." inside it: made while your property was simulating. "Queen $150.00 to $165.00", "$165.00 after this run": a room type's price before and after the run that made it. "Prices not on record": that run's record is missing. "at your ceiling": your limit held it. "Show 50 more" and "of 50 nights and room types left.": a fire across more than 200; click to list the rest, 200 at a time. "The rule has been edited since.": only the numbers it fired on are shown. "Came off Oct 5, 9:10 AM: bookings behind it cancelled.", "Would have come off ...", "Moved to the rule's new amount ...", "A price set by hand took over ...", "Told to stop on this night ...": what happened to it later. "This rule is off. Its changes stay where they are.": the rule is switched off. "No fires in the last 90 days.", "Nothing older. The fire log shows the last 90 days.", "Couldn't load this rule's fires.", "Couldn't load older fires.": what the window has, or could not load. The fire log
"Sellable occupancy above 80%", "Booking window below 7 days", "Pickup above 5 room nights", "booking speed at least Much Faster Than Normal (past week), then waits 2 days": the conditions column.
"Watches Standard, Deluxe · Changes Suite": the rule measures one set and changes another.
"+10%", "-$25": the price change column. A fixed amount shows your property's currency sign, such as "+€25".
"On" / "Off": the status switch. Off keeps the changes the rule made. On opens the window with the days first. Off, delete or change
"Stopped on 3 nights" with "Let it run again": you told the rule to stop on those nights from the amber banner. The link puts it back. Rules that keep adjusting
"Delete "Busy nights"?" with "Delete Rule and Undo Its Changes" / "Turn It Off and Keep Its Changes" / "Cancel", and "Deleting cannot be undone.": delete reverts every change the rule made; off keeps them.

The Rate Simulator

Show the 11 messages

"Make up a night and see what your rules would do to it.": nothing here is saved or sent. "The math is the same a real run uses, so what you see is what your rules would produce for these numbers." The Rate Simulator
"Stay date" with "Sets days to arrival" (and which date windows and weekdays apply): pick a future night.
"Booking speed" with "Not enough history": leave it and rules stay quiet, as a real run keeps them quiet when there isn't enough history to read a pace. Pick a level to see them act.
"Base price", "Occupancy", "Picked up", "Guardrails": per room type inputs and the floor and ceiling.
"Rules in play": every rule, on or off, each with a tick box. The small tags: "event" is a booking speed or pickup rule, "ladder" is a (no booking speed or condition), "off" means the rule is switched off and "fires" means a ticked rule acts on the night you made up.
"+ Build a test rule" / "Discard test rule": a draft that exists only on this screen. "Save This Rule" saves it switched Off: "Rule Added to Rules Tab and Initialized as Disabled".
"Give the rule a condition, an amount, and at least one room type first.": the draft is incomplete.
"What would happen" with "held at your floor" / "held at your ceiling", "Rules asked for $320.00.", "No rule fires on this night": the result per room type.
"Didn't fire" with "Conditions not met", "No occupancy for its signal room types", "No booked so far vs usual entered", "Rule has no room types attached", "Outside the rule's date window", "This day of the week is excluded": why a rule stayed quiet. A rule did not fire
"The math is the same a real run uses, but this preview simplifies three things": the note under the results, on where one made-up run differs from a real night. The Rate Simulator
"This property has no active room types yet.": connect and finish the import first.

The calendar and prices you type

Show the 36 messages

"Updated 3:05:12 PM · live": when the calendar last refreshed, to the second, on your browser's clock and in its time format. "live" means the calendar refreshes by itself when prices or bookings change. It does not mean prices are being sent, and it shows in simulation too. "Loading…" while it loads. The calendar
"Strong night", "Typical night", "Weak night": the colour key on the left of the calendar, by revenue per room against your own nights. On a phone it reads just "Strong", "Typical" and "Weak". Its ?, "What the colours mean", says how a night is judged. Calendar and change log questions
"Weak night, keep working on it" beside green and "Strong night, leave it" beside red: the same key on a property that reversed its colours in Settings. Settings
"ADR $182", "RevPAR $109", "Price $165" (or "Price –") on a day: numbers your property picked for the calendar in Settings. A dash means there is nothing to show that night, such as no published price. Settings
"12/20 rooms · 60% sellable occupancy · revenue on the books $2,400.00": booked over sellable, the percentage, and room revenue. "revenue" alone on past days.
"12 booked, usually 7 by now", "Standard and Deluxe: 9 booked, usually 5.5 by now", "12 booked, usually 6.5 to 7 by now" and "12 booked. Not enough similar nights to compare with yet.": under that line, for a night a booked so far vs usual rule that is on covers. The calendar
"Booked 8/12", "ADR $150.00", "Current price $165.00" (or "Current price" followed by a dash), "Revenue $1,200.00": the room type card, with your property's currency sign. A dash means no price published for that night. A price looks wrong
"Manual · $180.00": a price someone typed. "Changed in Cloudbeds · $180.00": a rate you changed in your system on a night MAYA had sent to. Setting a price yourself
"Rate removed in Cloudbeds, so MAYA isn't pricing this night" with a ?: your system no longer has a rate for a night MAYA had sent to, and your property keeps changes made there, so MAYA prices and sends nothing for it until your system has a rate again. Its ? is "A rate removed". A rate removed in your system
"Or type a price here. A price you type is sent as it is.", or "Or type a price here. Once you go live, a price you type is sent as it is." while simulating: the last line behind the ? of "No rate in Cloudbeds for this night yet" and of a rate removed. Setting a price yourself
"through…": type one price for a range of nights. "×" goes back to one night.
"Save" and "Clear": save the price; hand the night back to your rules.
"Setting a price yourself": the help panel beside the price box, a short version of the page of the same name. Setting a price yourself
"Saved. Sending to Cloudbeds now.": sent straight away. "Saved. Sending to Cloudbeds on the next cycle (about 5 min).": on the next run. "Saved. MAYA doesn't send prices to Mews yet.": a live Mews property, where nothing is sent.
"Saved (simulation: not sent to Cloudbeds).": you are simulating. Simulation mode
"Saved. It will be sent when the date enters the 396-day push window.": every night you saved is past the window of tonight and the next 395 nights, so 396 or more nights ahead. Each is sent once it enters the window.
"Saved. 12 nights sending to Cloudbeds now; 8 more will be sent as they enter the 396-day window.": a range across the edge of the window.
"Saved. MAYA doesn't send a price of 0 to Cloudbeds, so set the night to 0 there yourself.": a . Make a night free
"Saved. It will be sent once you reconnect.": you are live and the connection reads Disconnected. Nothing is sent until someone reconnects. Connection lost
"Saved. Cloudbeds isn't answering MAYA right now. MAYA keeps trying to reach it and sends this price as soon as it answers.": you are live and the connection reads Error. MAYA keeps trying to read from your system, and the first read that works sends the price on that cycle. Reconnect if it has not cleared within a couple of hours. Connection lost
"Accepted by Think Reservations, checking.": ThinkReservations took the price, and MAYA's hourly read of your rates has not found it there yet. It changes to "Sent to Think Reservations." once it does. ThinkReservations
"Sent to Cloudbeds.", "Sending to Cloudbeds now.", "Saved. It couldn't be sent yet. MAYA will retry 3 more times." and "This price couldn't be sent to Cloudbeds.": what became of the price after the save, read from MAYA's own record of the sends: taken (accepted, on ThinkReservations), on its way, refused for a cause that clears on its own with the real count of tries left at this price, or stopped. "Try again" under the last one sends the price once more now (Revenue Manager or higher). "See the error log" opens the change log at the sending problem for that night; until the change log shows one, the cause is written under the line instead. The last line with no "Try again", even for a Revenue Manager, means the room type has no rate in your system for MAYA to send to, such as no . Setting a price yourself
"Saved." on its own: MAYA could not read your mode or your connection just then. The price is saved, and the next cycle sends it if you are live and connected. The PMS tab shows the connection.
"Saved. Nothing is sent while MAYA's work is paused. Update your card on the Billing page.": your subscription is Unpaid. "Restart your subscription on the Billing page." in place of the last sentence when it reads Cancelled or Never completed, and "Email us and we'll get it running again." when it is on hold. Cards, payments and invoices
"Paused 2 rules on this night for this room; new rules will apply on top." and "No rule raises a night set to 0.": what the save did to your rules.
"Cleared. Your rules price this night again." and "Cleared 5 nights. Your rules price them again.": the night is back with your rules.
"This night has passed, so there is nothing to clear.": the night passed while the calendar was open. Nothing changed. A past night shows no Clear.
"Couldn't save that price.", "Couldn't clear that price.", "Couldn't reach MAYA. Try again.": the save did not go through. Try again.
"This needs Revenue Manager access or higher on this property.": Viewers cannot type prices, take or answer the banner. Roles
"That's a lot of price changes at once. Give it a minute and try again.": 30 saves or clears per person per 10 minutes.
"Price must be a number of zero or more.", "That price is more than MAYA can store.": type a number from 0 up to 99,999,999.99.
"Start date must be a real date (YYYY-MM-DD).", "End date must be a real date (YYYY-MM-DD).", "End date can't be before the start date.", "One change can cover at most 366 nights.": fix the range.
"Manual prices apply to tonight onwards; earlier nights have already sold.": past nights cannot take a price.
"You can set a price up to 400 nights ahead.": the last night is more than 399 days out.
"Below this room type's floor of $80.00." and "Above this room type's ceiling of $300.00.": refused, not rounded. Change the limit if you mean it. 0 is allowed as a comp night.
"Pick a property first.", "Pick a room type.", "That room type isn't on this property.": reload and try again.

Settings

Show the 18 messages

"Settings": opened from the gear at the top right of the dashboard. "Calendar" reads "For everyone on" and your property's name; "Display" reads "Just for you". Settings
"Cloudbeds" (or "Think Reservations") with "When a price MAYA sent is changed in Cloudbeds", "Keep the change as your price" and "MAYA's price wins": what MAYA does with a rate changed or removed in your system on a night it sent to, for everyone on the property. Its ? is "What the two choices do". Changes made in your property system
"3 nights keep a rate changed in Cloudbeds. MAYA will replace them with its prices." with "Replace them" and "Cancel": you chose MAYA's price wins while some nights ahead keep a rate changed in your system. Nothing is saved until you press Replace them. Turning MAYA's price wins on
"Pick one of the two choices." and "Could not save this setting. Try again in a moment.": the property system setting, or a bookings setting, did not save, and the choice went back. Try again.
"Big number", "First small line", "Second small line" with "None", and "Price for": what each day on the calendar shows, for everyone on the property. What each day shows
"Colours" with "Standard" and "Reversed": which colour marks a strong night and which a weak one. Colours
"Text size" with "Standard", "Large" and "Larger": your own text size, on every device you sign in on. Text size
"Bookings" with "Count bookings made together as one", and under "Advanced" "Count a group as up to" a number "bookings": how counts bookings made together and groups, for everyone on the property. Their ?s are "What counts as made together" and "How this works". Bookings
"Starts once MAYA has re-read your booking history." under Count bookings made together as one, once it is ticked: MAYA has not read the time your past bookings were made yet, so each still counts on its own. Its ? says how it is read. Bookings made together
"Pick a whole number from 1 to 10.": Count a group as up to takes a whole number from 1 to 10. The box went back to the saved number. Count a group as up to
"Not saved" beside Count a group as up to: you scrolled while typing in the box, so it let go without saving. Click back in and press Enter. Count a group as up to
"Saving…" and "Saved": beside a section's heading, as a change saves.
"Only a Revenue Manager or above can change these.": the calendar, property system and bookings sections are greyed out for your role. Your text size is still yours to change. Roles
"Pick a big number from the list.", "Pick up to 2 small lines from the list.", "Each number can show once on a day.", "Pick Standard or Reversed colours.", "Pick the room type whose price to show.", "Pick a room type from the list.": the calendar could not take that choice, and the list went back to what was saved. Reload and try again.
"Could not save your calendar settings. Try again in a moment.", "Could not save. Try again in a moment.", "Could not save. Check your connection and try again.": the change did not go through, and the list went back. Try again.
"Couldn't save your text size. Try again.": the size shows on this page, but could not be saved with your login, so the dashboard goes back to your saved size next time. Choose it again.
"Couldn't load your settings. Close this and try again in a moment.": Settings could not read what is saved. Close it and open it again.
"Couldn't load these settings. Close this and try again in a moment." under "Calendar": Settings could not read your property's calendar choices just now, so the section stays greyed out. Close Settings and open it again. Settings

Room types, on the PMS tab

Show the 16 messages

"Room types" with "What counts as a room": ticked types are what MAYA divides by: , revenue per room and the room count you are billed for. Room types and rooms out of service
"Counts as a room" and the tag "not a room": the checkbox per room type. "6 units": the room count read from your system; 100 when MAYA has none.
"A General Manager or Hotel Admin can change which room types count as rooms." behind the ?, with the boxes greyed out: your role can see the ticks but not change them. "This needs General Manager access or higher on this property.": a change sent from below General Manager was refused. Roles
"needs your answer": a tag on an unticked room type nobody has ticked or unticked yet. It counts in occupancy but not in your bill until you answer. Room types and rooms out of service
"1 change not saved" with "Save" and "Discard", and "Not saved" beside a box: ticks wait for Save, which saves them all and checks your billed room count again. Discard puts the boxes back. Saving your answers
"Saved.", or "Saved. 22 rooms are counted and you're billed for 20.": the save went through. The second says more rooms are still counted than you pay for, so the billing banner stays. Two ways to fix it
"That didn't save. Try again." (or the reason): the save did not go through. The changes that did not save stay, with Save.
"No room types have synced yet." and "Couldn't load room types.": wait for the first read, or press Try again.
"+ Rooms out of service" with "From", "To", "Units", "Reason (optional)", "Save", "Cancel": take rooms off sale for a stretch. Nothing is sent to your system. Tell MAYA rooms are out of service
"3 out of service", "2026-11-10 → 2026-11-14", "· Renovation", "Clear": an existing block and its link to end it.
"One block can cover at most 366 nights.", "Units must be a whole number of at least 1.", "Keep the reason under 200 characters.": fix the form.
"Standard has 12 rooms" (you can't block more than that) and "Standard already has 8 rooms out of service on some of those nights" (that leaves 4 you can still block): blocks stack per night up to the room count.
"That block is already cleared." and "Pick a block to clear.": the block is gone already, or none was chosen.
"That's a lot of changes at once. Give it a minute and try again." and "That's a lot of room-type changes at once. Give it a minute and try again.": the same limit as .
"Something went wrong on our side. Try again in a moment.": try again.
"Something on our side isn't ready yet. Email us and tell us which page you were on.": what it says. Email us with the page you were on. The same message can appear when you type a price, press Try again on one, or set a property aside with "Not now".

The change log

Show the 41 messages

"Change Log" with "Show All Cycles" / "Show Changes Only": every run, the quiet ones counted into lines, or only runs that changed something. The change log
"Pricing run · Fri, Sep 18, 2026, 3:05 PM PDT" with "(3 min ago)", "(yesterday)": one run, in your browser's time zone.
"Prices checked 47 times from Sep 24, 10:05 AM to 1:55 PM, nothing needed to change." and "Just before that, prices were checked 12 times ... and nothing needed to change.": a stretch of runs that changed nothing, one line each, under "Show All Cycles".
"Couldn't load your price history." with "Try again": the log could not be fetched.
"Older" under the last item: adds the 10 runs that changed a price before the ones shown. "Couldn't load older history.": that page could not be fetched; click Older again. "Nothing older. History is kept for 90 days.": you have reached the oldest run kept. How much the log shows
"Rough estimate since Sep 21: you've added about $966 with MAYA's prices." under Older: what MAYA's prices added, from bookings already made. While prices aren't sent (in simulation, on Mews, or with sending switched off), "you would have added about $966"; both kinds, "you added about $1,210 with MAYA's prices while live, and would have added about $1,130 in simulation." or "... while they were sent, and would have added about $1,130 while they weren't." Nothing yet: "Rough estimate: you haven't added anything with MAYA's prices yet.", or "you wouldn't have added anything". Its ? opens "How it's worked out". "Rough estimate: working it out…": wait a moment. "Couldn't work out the rough estimate." with "Try again": click it. The rough estimate
"Nov 14 · 7 room types · Busy nights +10%": the bold line of one change: the night, the room types it moved the same way, and what changed in that run. "Weekend nudge +10% came off", "Cloudbeds' rate changed", "Price set by hand": other things a run can change. "Each room type": opens each room type's price before and after. "Sudden-spike catcher's +25% still applies." in grey: a change already on the price that this run left alone. A change, line by line
"Simulation" beside a run's time, and a bold line starting "Simulation:", such as "Simulation: Nov 13 · Standard · Busy nights +10%": a run made while your property was simulating. Nothing in it was sent, and it stays labelled after you go live. Its sentences say "would have raised", "would have lowered", "would have come off", "so it would have stopped there", "That would have taken this night from $165.00 to $150.00." and "The price would have moved from $150.00 to $160.00." Runs made in simulation
"Nothing was sent to Cloudbeds." under a bold line: a simulated change; "Nothing was sent to Cloudbeds at the time." once you are live. "Sent to Cloudbeds after you went live.", "Waiting to be sent to Cloudbeds now that you're live.", "Couldn't be sent to Cloudbeds after you went live.", "Held back after you went live, not sent to Cloudbeds.": a second line under a simulated change whose price the night still has, saying what going live did with it. Runs made in simulation "Sent to Cloudbeds.": a live price that went. "Accepted by Think Reservations, checking." (and "... after you went live, checking."): ThinkReservations took the price, and MAYA's hourly read has not found it there yet. "Waiting to be sent to Cloudbeds.": not sent yet. "Couldn't be sent to Cloudbeds.": MAYA stopped trying. "Held back, not sent to Cloudbeds.": held back on purpose, or no rate in your system to send to. "Nothing was sent to Mews. MAYA doesn't send prices there yet.": a live Mews property. An older change has no such line, and nor does an unsent price while MAYA can't send it. Where the price went
"And 23 more changes in this run.", or "And 23 more prices would have changed in this run." in a simulated run: the moves past the 40 biggest, counted.
"Went live" with "Sam took pricing live. From the next cycle, MAYA sends its prices to Cloudbeds.", and "Back to simulation" with "Sam switched pricing back to simulation. MAYA stopped sending prices to Cloudbeds.": someone on your property switched the mode then. Going live and back
"That change is further down. Click Older to find it.": a link to a change that is on an older page. "That change is no longer in the change log. History is kept for 90 days.": it is older than the log goes back.
""Busy nights" raised this night 10%, from $150.00 to $165.00." and ""Last minute" lowered this night 15%, from ... to ...": a rule fired in this run, from the price the night had just before. "on 7 of 8 room types": the prices most of the line's room types share; Each room type has the rest.
"Cloudbeds' rate went from $296.00 to $336.00, so the price moved to $420.00.": your own rate changed in your system, and the rules already on the night stayed on it.
"It was 82% full, past the 70% mark you set.", "under the 40% mark you set", "It had 5 days to go, past the 7-day mark you set.", "beyond the 21-day mark you set", "It was 95% full with 17 days to go, past the 90% and 21-day marks you set.": why a rule with an occupancy or condition acted. Fewer days than the mark reads as "past".
"Standard and Deluxe were 92% full, past the 90% mark you set.": the rule measures other room types than it changes.
"9 room nights booked over the last 3 days, past the 4-room-night mark you set.": why a pickup rule acted, over its lookback ("over the last 30 days", or "over the last 3 full days" for a rule set to Less than). "6 room nights booked since this rule or a stronger one's latest raise still on this night": it counted only from that change. "2 more room nights cancelled than booked": the count was under zero. "past the 500 revenue mark": a revenue rule, with your amount as the mark.
"Bookings came in faster than normal this past week: 9, against the 5 a night like this usually has by now.": why a rule acted. Variants: "Bookings surged", "Bookings all but stopped", "Bookings came in at the normal pace", "much slower than normal", "this past day", "this past month", and for a rule that cuts "in the month up to yesterday". Booking speed reads oddly
"6 reservations in one Think Reservations group counted as one booking." (or "9 reservations in 2 Cloudbeds groups counted as 2 bookings."): a group counted once for booking speed. Pickup and occupancy count each room. With Count a group as up to above 1 in Settings, "10 reservations in one Cloudbeds group counted as 3 bookings." What is counted
"4 bookings made together for the same dates were counted as one." (or "... were counted as 3.", and "9 bookings made together for the same dates, in 2 groups, were counted as 2."): separate reservations for the same room type and dates, made within 3 hours of each other, counted as one booking for booking speed, because Count bookings made together as one is on in Settings. Pickup and occupancy count each room. What is counted
"in the 4 days since this rule or a stronger one's latest raise still on this night", "later on the day of this rule or a stronger one's latest raise still on this night", "in the 3 full days after this rule or a stronger one's latest cut still on this night", "usually gets in those days", "usually gets in a day": the rule counted only the bookings made since the newest change on the night by itself or a stronger rule that moves the price the same way. "usually gets in a whole week": a rule that raises on a fast pace, whose bookings since that change had to beat a whole week of a similar night.
"none, where a night like this usually has almost none by now": no bookings, against an expectation under 1.
"It had 12 of its 20 rooms booked with 30 days to go, where similar nights usually had 7 by then: 5 more, reaching the 25% mark you set.": a booked so far vs usual rule's reading. Booked so far vs usual
"That 95% leaves out Kayak Store.": a measured type that is not a room was left out of the figure.
"That would have gone past your $300.00 ceiling for Standard, so it stopped there." and "That would have dropped under your $80.00 floor for Standard, so it stopped there.": the limit stepped in. "...further past your $300.00 ceiling for Standard than the price it started from, so it stopped there.": the price started from a already beyond the limit.
"Your floor for Standard went from $80.00 to $90.00, so the price moved to $90.00.": a floor or ceiling you changed moved the price.
"The price moved from $200.00 to $210.00.": the price moved and nothing on the night can be named, for example when MAYA has no record of the night's earlier run. A price looks wrong
"Cancellations meant "Warm-date bump" was no longer true, so its 10% raise came off.": guests cancelled and the rule's undo box is ticked. The numbers follow: "Of the 9 bookings it counted, 4 are still booked, where nights like it usually get about 5, and the rule needs a booking speed of at least faster than normal.", "The pickup it counted was down to 4 room nights, and the rule needs more than 4 room nights." or "Sellable occupancy had fallen to 75%, and the rule needs more than 80%." When a change comes off
""Warm-date bump" stopped applying an earlier 10% raise here: this night's price was set by hand." and "...: this night no longer met its conditions." and "...: there weren't enough similar nights to compare with.": a change came off for that reason. ""Weekend nudge" was deleted, so its 10% raise came off.": the rule was deleted. "That took this night from $165.00 to $150.00.": the move, from the price the night had just before. "The price set by hand was cleared.": a typed price was cleared.
"the rule was edited, so MAYA started it fresh": someone edited the booking speed or pickup rule and chose Apply price adjustments, so its earlier changes came off and it read the night again. After an edit saved with Skip price adjustments, the same line shows later, once a held night stops being true and then becomes true again. On a it means a change that Skip kept at its old amount moved to the edited amount. The change log does not say who. Change a rule
""Weekend nudge" was edited, so its raise went from 10% to 15%.", with the bold line "Weekend nudge edited, +10% to +15%": a standard rule edited with Apply price adjustments while it still holds; its change moved to the new amount, and it did not fire again. Change a rule
"The 10% raise from "Busy nights" applies again.", with "Busy nights +10% applies again" in the bold line: a price set by hand was cleared, so the standard rule's change that was already on the night is back. It did not fire again.
"so two of its 25% raises came off", with "came off twice" in the bold line: two raises of one rule came off in the same run, for the same reason.
"Sam set the base rate to $180.00." under a bold line ending "Price set by hand": a typed price. "Sam typed a price of $180.00.": a price typed while simulating. "The base rate was changed in Cloudbeds to $180.00." under "Changed in Cloudbeds": a rate you changed in your system on a sent night. "A manager": the name is not on file. "MAYA support set the base rate to $180.00.": a price our staff typed for you.
"Changed in Cloudbeds · Fri, Sep 18, 2026, 3:05 PM PDT" with "Fri, Nov 13, Standard: changed in Cloudbeds to $175.00. MAYA sent its price, $165.00, again." (or "the rate was removed in Cloudbeds"): your setting is MAYA's price wins, so MAYA sent its own price again over a rate changed in your system, as its record of sends shows. On ThinkReservations it adds "Accepted by Think Reservations, checking." until MAYA's hourly read finds the price there. Until then it reads "MAYA's price, $165.00, is waiting to be sent again."; if MAYA stopped trying, "couldn't be sent again."; held back, "was held back, not sent."; and "was due to go out again." when it doesn't say how the send went, for example once a later price or change has replaced it. "And 12 more times MAYA's price was due to go out again over a rate changed in Cloudbeds.": the ones not listed. When MAYA's price wins
"Deluxe is no longer in Cloudbeds. MAYA stopped pricing it, and its rooms no longer count toward your occupancy or your bill." under "Changed in Cloudbeds": MAYA's daily read no longer found that room type in Cloudbeds, so MAYA switched it off. Nothing about it is deleted. "Deluxe is back in Cloudbeds. MAYA prices it again, and its rooms count toward your occupancy and your bill.": it is listed again, and back on. Room types and rooms out of service
"Your time zone changed from America/Denver to America/Chicago, to match Cloudbeds. Tonight and every rule's dates follow it." under "Changed in Cloudbeds": the daily read found a different time zone in Cloudbeds and MAYA follows it. "Your currency changed from USD to CAD, to match Cloudbeds. Amounts in MAYA are now in CAD; nothing was converted.": the same for the currency, only while you are in simulation. Time, weekends, currency and holidays
"Something other than MAYA seems to be changing rates in Cloudbeds: 34 rates changed in the last 7 days on nights MAYA had sent a price to." with "Open the setting": many rates in your system changed like another pricing tool's work, and your property keeps them as its prices. The button opens Settings at your system's section. When something else seems to change your rates
"Changed by MAYA support · Fri, Sep 18, 2026, 3:05 PM PDT" with one line under it, such as "Changed by MAYA support: Took pricing live." or "Changed by MAYA support: Set the rate type MAYA reads and writes to Best Available Rate." (or "... back to automatic."), "Changed by MAYA support: Set MAYA to move Harbour Wedding too." or "Changed by MAYA support: Left Harbour Wedding out of MAYA's moves.": a change our staff made to your property for you, in a support mode that records every change. The change log
"Pricing rule" and "A rule": a rule that has since been deleted.
"Your answer · Fri, Sep 18, 2026, 3:05 PM PDT", or "MAYA support's answer" when our staff answered for you: an answer to the amber banner, with one line under it. Stopping a rule: "Priya stopped "Hot-week surge" on 4 nights. What it already changed stays, unless cancellations mean the rule is no longer true." With its undo box unticked: "Priya stopped "Slow-date rescue" on 4 nights. What it already changed stays." Answered while simulating: "Its simulated changes so far stay, ..." in place of "What it already changed stays". Carrying on: "Priya told "Slow-date rescue" to carry on with 4 nights." Letting it run again: "Priya let "Slow-date rescue" run again on 4 nights. It can start adjusting again from the next pricing run." Rules that keep adjusting

"Show the numbers" and setting a date aside

Show the 25 messages

"Show the numbers": opens the or booked so far vs usual reading behind a change. "Loading the numbers from that run…" while it loads. "Booking speed" and "Booked so far vs usual" head the blocks when a change carries both. The numbers behind a change
"No booking numbers were saved for this change.": the record behind this change holds no reading MAYA can show. If you were looking for one, email us the night and room type.
"Could not load the details" with "Try again": the Show the numbers panel could not load. Press Try again.
"In the last 7 days, 9 bookings arrived for this night, with 40 days still to go before arrival.": what was counted. "9 Standard and Deluxe bookings": over the rule's measured types.
"The newest raise still on this night's price, by the rule behind this reading or a stronger rule, was made on Fri, Nov 13 2026. In the 4 days from that raise on, 12 bookings arrived for it, with 20 days still to go before arrival.": the count started at that raise, and bookings later that same day count too. When the raise was earlier the same day, it reads "Later that day," instead. After a cut: "In the 3 full days after that, up to yesterday,". A rule that cuts with no change to count from: "In the 30 full days up to yesterday,".
"By this point, nights like this one usually get about 5 bookings over the same stretch.", "...over a whole week." and "...almost no bookings...": what had received. "Over a whole week" is the bar for a rule that raises on a fast pace.
"There isn't enough booking history yet to say what is usual for this night." and "Booking speed wasn't rated for this night, so rules that watch booking speed left it alone.": not enough history.
"That reads as Faster Than Normal.": the level.
"The numbers leaned away from Normal, but by too little to matter at this many bookings, so it stays Normal.", "The numbers pointed one step further from Normal, but not clearly enough, so it reads one step closer to Normal.", "Only a few similar nights were found, so it stays within one step of Normal however strong the numbers look.": a check kept the reading nearer Normal. Booking speed reads oddly
"Which nights were compared?": how the similar nights were chosen. Lines: "Once a rule or a stronger one has raised this night, it counts only the bookings made after the newest of those raises still on the price, the rest of that day included, and reads the nights it is compared with over the same days. A weaker rule's raise, or any cut, doesn't move where it starts.", "A rule that cuts counts full days only, up to yesterday, on this night and on the nights it is compared with alike.", "Only other Friday nights were compared, since each night of the week books in its own way.", "Too few other Friday nights matched, so Saturday nights were compared too, since they are also weekend nights. Friday and Saturday nights count as weekend nights, the rest as weekday nights.", "Around Christmas the day of the week changes from year to year, so the nights compared fall on Tuesday, Thursday and Friday.", "This night is near Thanksgiving, so it is compared with the same days around Thanksgiving in earlier years, not the same date.", "Only nights in the same season of your history were compared: Peak Season (June 10 through August 31)." (or, when nights from around the same time of year were added, "Too few matched there, so nights within 45 days of the same time of year were added."), "Fewer than 4 nights matched closely, so the search was widened. Check the nights below and set aside any that were not normal.", "Closed periods, and any nights you have set aside as not normal, are never compared." Similar nights
"Your history has no usable similar nights for this one, so the usual number comes from booking momentum instead.", "Momentum here means how nights near this one are filling now, compared with how the same nights were filling at this point last year.", "3 nearby nights could be paired with the same nights last year.", "Those nights are filling about 20% faster than they were a year ago.", "The starting point was about 4 bookings, taken from how this same night was booking at this point last year.", "Momentum is rougher than comparing similar nights, so treat it as a best effort, not a measurement.": the fallback when no similar nights exist.
"There wasn't enough history to say what is usual, so no rule acted on booking speed for this night.": the same, in the list under Which nights were compared?.
"12 of this night's 20 rooms to sell were booked, with 30 days still to go before arrival.", "By this point, similar nights usually had 7 rooms booked.", "That is 5 more than usual: 25% of the rooms to sell.": a booked so far vs usual reading. With too few similar nights: "There aren't enough similar nights to compare with yet: 2 could be compared, and 3 are needed." and "Rules on booked so far vs usual left this night alone." Under Which nights were compared? it adds "Each similar night is read at the same number of days before arrival, up to the end of that day, for a rule on ahead." (or "up to the start of that day, for a rule on behind."), and under List the nights each night reads "7 of 20 rooms booked by then", or "left out: ..." with the reason. The numbers behind a change
"List the nights": one row per similar night: "Fri, Jul 18 2025" with "4 bookings in the same stretch" or "no history for this night", and reasons such as "a Friday; your Peak Season; about a year earlier" or "a Saturday, similar to a Friday".
"Not a fair comparison?": set that night aside. "What made Fri, Jul 18 2025 not a fair comparison?" with "Choose a reason…": Holiday Not on MAYA's List, Local Event or Festival, Sporting Event or Tournament, Conference or Convention, Renovation or , Utility or Amenity Outage, Group Buyout, Nearby Competitor Closed or Sold Out, Severe Weather, Road, Transit, or Flight Disruption, Booking Data Looks Wrong, Other. Not a fair comparison
"Tell us in a few words what happened": the text box for Other, up to 300 characters.
The three scope options: the first sets aside this one date (recommended); "This happens every year around this time" also counts toward a yearly pattern, which needs reports from 2 different years; "This should also change how our seasons are read (advanced)" also counts toward how seasons are read, which needs reports from 3 different years.
"Set this date aside" / "Saving…" / "Never mind": save or cancel. Needs Revenue Manager or higher.
"Set aside. Not used from the next run on.": the night is out of comparisons from the next run.
"You have already flagged this date for that reason": it is already set aside.
""Group Buyout" cannot be generalized that far" (flag only the date instead): that reason only allows the one date.
""Other" needs a short explanation", "Keep the explanation under 300 characters", "That is not a real calendar date", "Unknown reason": fix the form.
"You need manager access to do that.": Revenue Manager or higher.
"Your corrections" with "Show" / "Hide": every date you have set aside. "You told us this date was affected by group buyout, so we leave it out of comparisons.", "We have seen this reported in 1 year of the 2 different years we would want before treating "Local Event or Festival" near June 10 as a pattern that repeats every year.", "Reports across 2 different years flagged "Local Event or Festival" near June 10, so we now leave it out of comparisons every year.": one line per correction.
"Undo" / "Removing…": makes the date comparable again from the next run. "Nothing was removed" (it may already be gone, or removing it needs manager access), "Could not load corrections", "Could not remove": try again.

"Prices not reaching", in the change log

Show the 7 messages

"Prices not reaching Cloudbeds": prices are not landing in your system. The item names the cause and what to do, and "Show 12 tries" (or "Show 3 checks") / "Hide tries" (or "Hide checks") list the tries behind it. When your property system does not accept a price has every sentence the item can show, with what to do.
"No rate to price from in Think Reservations": the same kind of item on a ThinkReservations property in simulation. A room type has no rate type MAYA can read, so it isn't priced. The rate type causes
"Think Reservations has more than one rate type MAYA could price Deluxe from, so it isn't priced." with "Pick the rate type MAYA reads and writes on the PMS tab.", and "More than one rate type could be the base in Think Reservations" on its tries: no rate type is named Best Available and two tie, so MAYA uses neither. Pick one on the PMS tab. The rate type causes
"The rate type picked for MAYA is gone or switched off in Think Reservations, so Deluxe isn't priced." with "Pick another rate type on the PMS tab.", and "The rate type picked is gone or switched off in Think Reservations" on its tries: the rate type picked on the PMS tab was removed, switched off or set to follow another. MAYA never swaps in another. Pick another, or Automatic.
"Think Reservations took Standard rates but never confirmed it saved them.": the old rate was still there 3 hours after a send, and the night has gone 6 hours like that. MAYA keeps sending it by itself until a read finds its price. Nothing to do. How a send is checked
"Think Reservations isn't taking MAYA's prices for Harbour Wedding on Deluxe" with "Check Harbour Wedding in Think Reservations.": ThinkReservations keeps refusing MAYA's sends to that one of your other standard rate types on that room type (with three or more, "3 of your other standard rates"). Your main rate is not affected. Check that rate type's settings in ThinkReservations, or untick it under Also moves with MAYA if you'd rather MAYA left it alone. When ThinkReservations refuses MAYA altogether (its permission to update rates, or not answering), this item doesn't show: the item about your main rate covers it. Your other standard rates
"Think Reservations took MAYA's prices for Harbour Wedding on Deluxe but never saved them": as above for a send ThinkReservations accepted and never applied, on one of your other standard rate types. MAYA keeps sending it by itself until a read finds its price. Nothing to do.

The "Rules that keep adjusting" banner

Show the 12 messages

"Rules that keep adjusting": three of a or pickup rule's changes are on the same night. It keeps going until you answer. Rules that keep adjusting
""Hot-week surge" has 3 raises on Fri, Nov 13 2026.", ""Slow-date rescue" has 3 cuts on each of 4 nights.", "3 to 5 cuts on each of 4 nights", "up to 5 cuts": the headline, counting the rule's changes still on the price. "would have": you are simulating.
"It keeps raising these nights until you stop it." / "It keeps cutting these nights until you stop it.": what happens while nobody answers.
"3 raises on Standard and 1 raise on Deluxe": the rule's changes still on the price, per room type on that night.
"In the 7 days it measured, 9 bookings came in. A night like this usually has about 5 by then.", "no bookings came in", "almost none": what the rule read at its latest change. "Since the raise before its latest one, by it or a stronger rule, 12 bookings came in. A night like this usually gets about 5 in a whole week.": a rule that raises on a fast pace counted only from an earlier raise.
"Pickup over the last 3 days came to 6 room nights, against the 4 you set.": a pickup rule's reading.
"If it keeps cutting, the price can fall to your $80.00 floor for Standard." and "If it keeps raising, the price can climb to your $400.00 ceiling for Deluxe.": how far the price can go.
"Your ceiling for Suite is still MAYA's $99,999.99 default, so the price can climb that far." and "Your floor for Standard is still MAYA's $1.00 default, so the price can fall that far.": no limit is set. "About this limit" explains; "Ask MAYA for a ceiling" / "Ask MAYA for a floor" takes you to the Rules tab.
"Keep adjusting" and "Stop for this night", "Keep adjusting on all 4 nights" and "Stop on all 4 nights": your two answers. "What each answer does" explains them.
"Fri, Nov 13 2026, Sat, Nov 14 2026, Sun, Nov 15 2026 and 9 more nights" with "Answer night by night" / "Hide the nights": several nights on one card.
"Only a Revenue Manager or above can answer this.": your role cannot answer.
"That did not save. Try again in a moment.", "Choose keep adjusting or stop.", "Pick the nights to answer for.", "Unknown alert.", "Let one rule run again at a time.", "Pick the rule to let run again.", "Pick the nights to let it run on.": try again.

The PMS tab and the connection

Show the 28 messages

"PMS": the tab. "Property System (Cloudbeds)" with "Bookings sync automatically on a schedule. This page shows how that connection is doing." The PMS tab
"Select a property to view status.", "Loading connection status…", "No property system is connected for this property yet.": no property chosen, still loading, or nothing connected.
"Connection" with "Connected", "Pending", "Degraded", "Error", "Disconnected", "unknown": the connection's state. Connection lost
"Health (last 24 hours)" with "Healthy" (98% or more of requests OK), "Degraded" (80% or more), "Having trouble" (under 80%), "No recent activity" (no requests recorded in the last 24 hours), and "97% of 412 requests OK". "Not tracked for this system" on ThinkReservations and Mews: MAYA keeps no log of its requests to them. Read Last sync instead.
"Last sync": the last successful booking read, on your browser's clock. A dash means none yet.
"Recent requests to Cloudbeds" and "No requests recorded yet" (the log fills as syncs run): MAYA's last 50 calls to Cloudbeds. "ERR" marks a call with no status code. On ThinkReservations and Mews the list reads "Not tracked for this system".
"MAYA has lost its connection to Cloudbeds" with "Reconnect Cloudbeds": the connection is gone. "Your prices aren't updating while this is down. Reconnecting takes one click and sends you to Cloudbeds to confirm. Your rules, history and settings are all untouched."
"Your Cloudbeds connection needs a refresh soon. Prices are still updating.": the connection reads Degraded. MAYA is still reading and sending. If the line is still there in an hour, a General Manager or Hotel Admin clicks the Reconnect Cloudbeds link at its end. Connection lost
"Your rules and settings are still here, and your booking history comes back once you reconnect.": a property that never paid and sat idle for 180 days had its booking history removed. Reconnecting imports it again. Privacy, security and your data
"Ask this property's General Manager or Hotel Admin to reconnect it": your role cannot reconnect.
"Mews needs its keys re-entered" with "Ask us to re-enter the Mews keys: email info@modern-hospitality-solutions.com.": every role sees this on Mews. Click the address to email us; Mews uses keys we enter with you.
"Reconnect Cloudbeds" as a small link on a working connection: reconnect any time; harmless.
"Time zone and currency", with the time zone's name and the currency's code and sign, such as "USD ($)": what is saved for your property, shown read-only. The PMS tab
"UTC and US dollars are what a property gets when its time zone and currency weren't read from its system. If either is wrong for your property, send us a message and we'll correct it." (or "UTC is what a property gets when its time zone wasn't read from its system."): check them against your system, and email us if either is wrong.
"MAYA checks both against Cloudbeds once a day and follows a new time zone. A new currency is followed only while you're in simulation." behind the ? beside Time zone and currency on a Cloudbeds property: what the daily read does with each. The PMS tab
"Reconnected.": a short note on the PMS tab after a successful reconnect. Nothing to do; close it with the ×. Connection lost
"You're signed out of MAYA": you opened the reconnect link while signed out. Press Sign in, then use the PMS tab.
"Cloudbeds wasn't reconnected" with "Reconnecting needs General Manager access or higher on this property. Ask its General Manager or Hotel Admin.": you opened a reconnect link without that role, so nothing was started. Ask a General Manager or Hotel Admin. Roles
"MAYA reads and writes: Best Available Rate": on the PMS tab, the review screen and the go-live confirm of a ThinkReservations property, the rate type MAYA reads your rates from and sends its prices to. Under it, "No rate type for Deluxe, so it isn't priced.", "Rack Rate and AAA could each be the base, so MAYA reads and writes none of them. Pick one.", "… are both named Best Available. MAYA uses …, the first Think Reservations lists. Pick one to be sure." (with several rate types in use, "… are both named Best Available for Standard and Deluxe. MAYA uses … for them, the first Think Reservations lists."), or "Rack 2025 is switched off in Think Reservations, so nothing is read or sent. Pick another." (also "... isn't in Think Reservations any more ..." and "... follows another rate type now ...") say what needs you. On the go-live confirm they end "Pick one on the PMS tab.", and for someone who can't pick, "A General Manager or Hotel Admin can pick one on the PMS tab." "MAYA reads and writes: no rate type": nothing can be read or sent until one of those is fixed. With several rate types in use, each is named with its room types, such as "MAYA reads and writes: Best Available (Standard and Deluxe) and Cottage Rate (Cottage)". Seeing and picking the rate type
"About the rate type" (the ? beside that line), titled "The rate type MAYA reads and writes": where MAYA reads your rates and, once you're live, sends its prices, and how Automatic chooses.
"Rate type" with "Automatic" and your active standard rate types: the list a General Manager or Hotel Admin uses to pick it. A pick that stopped working shows as "Rack 2025 (not usable)" until you pick another. Seeing and picking the rate type
"From the next cycle, MAYA reads and sends to Rack Rate. Best Available Rate keeps the prices MAYA last sent it, and rate types that follow it stop moving with MAYA." with "Switch" and "Cancel": a new pick on a live property, asked before it saves.
"Also moves with MAYA" under that line, with a tick beside each of your other standard rate types MAYA moves, "Standard and Deluxe only" beside one that covers only some room types, and "New" with "Leave out" beside one nobody has looked at yet (held out). "Not moved on 120 nights MAYA priced it as your main rate" beside a ticked one that used to be your main rate: those nights keep MAYA's last price. "About the other rates" (its ?), titled "Your other standard rates": "These rates get the same change MAYA makes to Best Available Rate, on their own rates: +15% adds 15%, and a fixed amount adds that same amount.", "Your floors and ceilings are for Best Available Rate only. Untick a rate to keep it as you set it in Think Reservations." and "Rates that follow another rate move with it, so they aren't listed." Below it for anyone who can't change it: "A General Manager or Hotel Admin can change this on the PMS tab." Your other standard rates
"From the next cycle, MAYA moves Harbour Wedding too, with the same change it makes to your main rate." with "Move it" and "Cancel", and "MAYA puts back Harbour Wedding's own rates and stops moving it." with "Leave it out" and "Cancel": a tick or untick on a live property, asked before it saves.
"MAYA also moves: Harbour Wedding and Garden Party Weekend." and "Held out: Lantern Group Block." on the go-live confirm: which of your other standard rate types move once you are live, and which are left out.
"MAYA moves up to 25 rates. Leave another out first.": a tick past the 25 MAYA moves. Untick another first.
"Only a General Manager or Hotel Admin can change this.", "MAYA hasn't read your rate types yet. Try again in a few minutes.", "Pick one of the rate types listed.", "Pick one of the rates listed.", "This property isn't connected to Think Reservations.", "This page is for another property. Reload and try again.", "Couldn't save that. Try again in a moment." and "Couldn't save that. Try again.": the pick did not save, and the line shows what is still in use. Reload, or try again in a few minutes.
"That's a lot of changes at once. Give it a minute and try again.", under the rate type or Also moves with MAYA: more than 6 picks and ticks by one person in 5 minutes. Nothing changed. Wait a few minutes and try again. Limits and numbers

Billing