A rule did not fire (or fired when you did not expect it)

Why didn't it fire?

Why didn't it fire? answers for one rule, one night and one of the room types the rule changes. On the Rules tab, a rule that hasn't fired in the last 90 days shows a dash in the Fired column: click the dash. A rule's fire log has a Why didn't it fire? link under its title, and Why this price? has Why not? beside each rule that isn't on. Pick the Rule, the Night and the Room type at the top.

It shows one line first, then only the other reasons that hold, each with a "?" that opens the docs about that reason. For example:

• "It's on this night: +10% since Oct 9, 2:15 PM."
• "It's Off. Its +10% from Oct 2 stays on the price: Off freezes, Delete removes."
• "At the last change here (Oct 9, 2:15 PM): Standard was 75% full. Your rule needs more than 80%."
• "It raised this night on Oct 8 and waits 7 days, until Oct 15."
• "At the last change here (Oct 9, 2:15 PM): The price was already at your $300.00 ceiling."

Show every check lists the checks it made, the ones that passed too; for a rule on the night now, or Off on a night MAYA is pricing, that is only whether it is switched on. Fire log opens the rule's fire log, and Try it in the simulator opens the Rate Simulator on that night with this rule ticked on its own: a what-if, not the reason.

Everything it says comes from what MAYA kept: whether the rule is on, what holds it back now, and its last reading on that night, named with its time. It never runs your rules again. A reading is kept only when a night's price or what is on it changes (What is kept), and a booking speed or pickup rule that isn't true leaves no reading of its own, so for one it says when it isn't in the night's last 10 changes. A rule on the night says since when only if its change has been on the price all that time. After you edited it while it held, or once a price set by hand paused it and was cleared, it says when it switched on here instead. A change made while your property was simulating says "(simulation)" after its time. Only while your property is still simulating does a rule on the night say "It's on this night in simulation" and "Nothing was sent.": going live sends every night's price, the changes made in simulation included. A night that has passed shows only what is kept about it.

The day card says 85% but my 80% rule did not fire

Two things to check.

Which room types the rule measures. The day card's occupancy (its big percentage, unless your property picked another number in Settings) is sellable occupancy over every room type ticked as a room. A rule reads occupancy over the room types in its own list. If a rule such as "Busy Standard" measures only Standard, and Standard is 75% full while Deluxe and Suite are full, the property reads 85% and the rule reads 75%. The Room Types column on the Rules tab shows the list, and "Watches Standard · Changes Suite" when the rule measures one set and changes another.

The comparison is strict. Greater than 80 fires at 80.01% and not at 80.00%. Less than 50 fires at 49.9% and not at 50.00%. To fire at exactly 80% as well, set the threshold to 79.99 (the box takes decimals). Read Greater than means more than.

Also check the rule's other conditions. A rule with occupancy and a booking window needs both true at once. "Busy nights" with a booking window Less than 7 added does nothing on a night 20 days out, however full it is.

The rule looks true but nothing happened

Work down these, or open Why didn't it fire? and the rule is checked against each of them for you. Most are visible on screen.

The rule is Off

The Status switch on the Rules tab. An Off rule is skipped on every night. Its changes already on the price stay there: Off freezes, Delete removes. On a night MAYA isn't pricing there is no price for them to stay on, so it says only "It's Off." and then why the night isn't priced.

It measures nothing

Only room types ticked as Counts as a room are measured. A rule whose measured list holds only a meeting room, a court or a spa slot reads nothing, so its sellable occupancy, rooms left, booking speed, booked so far vs usual, pickup count, current rate and average rate booked conditions can never be true. Booking window and recent bookings read no room types, so a rule whose only conditions are those keeps acting. A room type switched off in MAYA (an empty duplicate hidden during the review, one Cloudbeds or ThinkReservations no longer lists, or one we switched off after you removed it from Mews) is dropped from the list too.

It changes nothing here

A rule needs at least one room type to change, and the builder refuses to save without one. A room type switched off in MAYA is never priced, so a rule that changes only that type does nothing. A room type you removed in your system stays priced until it is switched off (on Cloudbeds by MAYA's next daily read, on ThinkReservations by the next cycle's read, on Mews by us), but nights that enter the 396-night window after you removed it have no rate to start from, so nothing fires on them (The night has no starting price).

It is waiting

A booking speed or pickup rule leaves a night alone for its wait after acting on it, from 1 day to 2 weeks (a pickup rule left on its lookback window, up to 30 days), per night and room type. A wait ends as a day begins at your property: a 7-day wait after a raise on Oct 8 ends as Oct 15 begins. A pickup rule set to Less than waits at least its whole lookback window, whatever wait you chose (How long a pickup rule waits). A price you type on the night starts the wait again for every rule that existed when you typed it, counted in whole days from the day you typed it. So does a rate changed in your system that MAYA keeps as set by hand: "A rate changed in Cloudbeds on Oct 10 started its wait again."

It counts only what came in after the latest raise

Once a night has been raised, a booking speed rule that raises counts from the newest raise still on that night by itself or a stronger booking speed or pickup rule, or a stronger rule's change that going live from your current rates took off. A weaker rule's raise never moves where it counts from. On the day of the raise, only the bookings that arrived after it count. A rule that raises on a fast pace needs those alone to beat what similar nights get in its whole window; any other rule compares them with similar nights over the same days. Cuts work the same way among the rules that cut, in full days up to yesterday. A raise by a standard rule (no booking speed or pickup count condition) never moves where counting starts. After a price you type, the rule reads its whole window again.

A stronger rule holds the night

Only one booking speed or pickup rule acts on a night and room type in a run. A stronger rule that is still waiting holds the night while it would be true again on the bookings since its own latest change, so a weaker rule that moves the price the same way can't act under it. It also holds a weaker rule that moves the price the other way while it is still true over its whole window. When two are ready at once, the stronger one acts. The bigger change to the price, in money, comes first. At the same change, a rule that watches booking speed comes before one that doesn't, and the faster speed before the slower for a raise (the slower first, for a cut). Then the pickup count that is harder to meet, then the starter rules before the rules you build, then the rule with more conditions, and last the older rule. Read which one fires when several match.

The price is already at the limit

A booking speed or pickup rule that raises does not fire on a night already at its ceiling, and one that cuts does not fire at its floor. Neither counts as a fire. A standard rule still switches on at the limit and counts as a fire, while the price stays at the ceiling or floor. A price you set yourself over the ceiling or under the floor is the limit for the rules on it: "The price was already at the $300.00 you typed, over your $250.00 ceiling."

Not enough history

A booking speed rule needs similar past nights, or failing those enough nearby nights to read momentum from. Momentum is how nearby nights are booking now compared with the same nights a year earlier. With neither it stays quiet. The change log's Show the numbers says "Booking speed wasn't rated for this night, so rules that watch booking speed left it alone."

No pickup reading from the window's start

A pickup count rule compares booked rooms now with booked rooms when its lookback window opened (1, 3, 7, 14 or 30 days ago). MAYA needs a reading from that moment for every room type the rule measures. A property that connected two days ago has no reading from 3 days ago, so a 3-day pickup rule stays quiet until it does, and a room type ticked as a room today has none either. A reading more than 12 hours older than the window's start still counts, unless MAYA ran no pricing at all in the 12 hours before the window opened (When pickup cannot be measured).

The night has no starting price

A night your system has at 0, or has no rate for at all, with no price typed in MAYA, is not priced, so nothing can fire on it. A booking's rate is never a starting price.

A standard rule is already holding

A standard rule (no booking speed or pickup count condition) fires once when its condition starts to hold, then holds. It does not fire again while the condition stays true, and the Fired count does not climb.

The night is outside the window

Your rules price tonight and the next 395 nights. Past nights are never touched.

A newer condition had nothing to read

A current rate condition has nothing to read on a night with no starting price (on Mews, a night without a typed price). An average rate booked condition has nothing to read on a night with no room booked at a rate above 0. A rooms left or booked so far vs usual condition has nothing to read when no room type it measures has rooms to sell. None of them is true then, whatever the mark.

Recent bookings is counted once a day

A recent bookings rule reads the count MAYA made at its first check of the day, over the full days up to yesterday. Bookings made today count from tomorrow. Read Recent bookings (advanced).

Not enough similar nights for booked so far vs usual

It needs at least 3 similar past nights with bookings, and a night near a holiday needs the same holiday in all three earlier years. With fewer it isn't true. The calendar's day card for the night says "Not enough similar nights to compare with yet." Read Booked so far vs usual.

Behind isn't true yet because of today's bookings

A Behind usual by at least rule counts today's bookings at once, and reads similar nights up to the start of the same day, so a booking made today can keep the night short of the mark. Read The same point before arrival.

It runs only on some nights

A rule can cover only some days of the week, or only some dates: a starter rule whose name ends in "(Fri and Sat)" or "(Sun to Thu)", or a rule imported from PIE with dates. The "?" after its conditions on the Rules tab says which. Rules you build in MAYA run every night.

Something you chose holds it

Three choices of yours hold a rule back on a night until it has stopped being true there and then becomes true again, or until you change your mind:

• Skip, when you switched it on or saved it: Turning a rule on.
• Going live from your current rates: Going live.
• A price you typed on the night, which pauses a standard rule that was already true: Setting a price yourself. A rate changed in your system on a night MAYA had sent a price to, which MAYA keeps as set by hand, does the same, and reads "A rate changed in Cloudbeds on Oct 5 paused it here." A night given away at $0 is never raised.

A fourth holds it longer: Stop for the night, when a rule kept adjusting it, holds that night until you click Let it run again or edit the rule, however often the rule stops and starts being true there: Rules that keep adjusting.

It fired on Deluxe but not Standard

Rules act per room type, so every hold in the list above applies room type by room type.

• Different ceilings and floors. For a booking speed or pickup rule, Standard's $300 ceiling may already be reached while Deluxe has room under its $400.
• Different waits. Each room type waits on its own. Standard may still be inside its wait from an earlier fire while Deluxe is free.
• Different counts. One rule reads the same count for every room type it changes, taken over the room types it measures. A booking speed or pickup rule's count differs between two room types only when the newest change it counts from, by itself or a stronger rule, was made at a different time on each, or you typed a price on one of them after that, which sends the rule back to its whole window there. To read each room type on its own, make one rule per room type, each measuring and changing only itself.
• A stronger rule holds Standard. Another rule may be waiting on Standard with its condition still true, which keeps weaker rules off that room type.

The change log lists each room type's change separately, so you can read the reason for the one that fired and look for the hold on the one that did not.

It fired 395 days out but not 397

Your rules price a window of 396 nights: tonight and the next 395, counted on your property's own calendar. A night 397 days out is not priced or sent, and no rule reads it. It enters the window the day after tomorrow, and rules act on it then.

You can type a price up to 399 days ahead. It is kept, and the night is priced and sent once it enters the window.

A rule that measures only the kayak store

Only room types ticked as Counts as a room are measured. Occupancy is rooms booked over rooms you can sell, and booking speed counts bookings, and neither is worked out for a court, a meeting room or a spa slot. A rule whose measured list holds only such types measures nothing, so its sellable occupancy, rooms left, booking speed, pickup count, current rate and average rate booked conditions never come true. Booking window and recent bookings read no room types, so a rule whose only conditions are those keeps acting.

It can still price the kayak store. Tick Change prices on different room types in the builder, put a real room type under Measure and the kayak store under Change. The rule then reads the room type's occupancy or booking speed and changes the kayak store's price. Read Measure one set of room types, change another.

When a rule measures a mix, MAYA drops the non-rooms from the figure and says so in the change log: "That 95% leaves out Kayak Store."

The Rate Simulator says "Conditions not met" or "No occupancy for its signal room types"

The Rate Simulator tab lists every rule that did not fire on a room type in its table under "Didn't fire", with one of these reasons:

The simulator's Booking speed select starts on "Not enough history", which keeps booking speed rules quiet, exactly as your booking speed rules do on a real night when there is not enough history. Pick a level to see what they would do.

The simulator differs from a real run in three ways it states on screen: a standard rule shows where the night settles rather than each step, every matching booking speed rule is added rather than one winner chosen, and a rule that would fire again after its wait is shown once. Read The Rate Simulator.

The rule changed the wrong room type

The room type list in the builder does two jobs. Unticked, Apply to room types is both the set the rule measures and the set it changes. Ticked, Change prices on different room types splits it into Measure and Change. The rule card reads "Watches Standard, Deluxe · Changes Suite" when the two differ.

If a rule changed a room type you did not expect, it is in that rule's Change list. Click Edit on the rule, untick it and click Save changes. With Apply price adjustments, the rule's changes come off that room type from the next run. Read Change a rule.

A Viewer's rule did not save

Viewers can look but not change. A Viewer who presses Add Rule or Save changes, flips a switch or presses Delete sees "Only a Revenue Manager or above can change this." in red, under the form or under the rule, and nothing is saved. Rules need Revenue Manager access or higher. Ask a General Manager or Hotel Admin to change your role on the Team page. Read Roles.

A rule I turned off still affects what another rule counts

Turning a rule Off freezes what it has done: its changes stay on the price. A change made by a booking speed or pickup rule that is Off also still marks where weaker rules start counting, because the bookings behind it were already acted on. Once a night carries a change, a booking speed or pickup rule counts only bookings made since the newest change still on that night by itself or a stronger booking speed or pickup rule moving the price the same way, switched-off rules included, or a stronger rule's change that going live from your current rates took off. Delete the rule if you want its changes and its marks gone.