> For the complete documentation index, see [llms.txt](https://revhero.gitbook.io/revhero-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://revhero.gitbook.io/revhero-docs/automation/event-log/event-types.md). # Event types The legend for the Event Log — what every Source and Action Type on a line means. Every line in the [Event Log](/revhero-docs/automation/event-log.md) has 1 **Source** and 1 **Action Type**, and records how it ended. ![One Event Log line: who did it, what changed, and whether it went through](https://272652298-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnzEa7YGji6t92Mfc0ZJ1%2Fuploads%2Fgit-blob-31fea4fff2f8afdb828350b0b7fee788d4e3c195%2Fanatomy-of-a-log-line.svg?alt=media) *Source tells you who, Action Type tells you what, and the ending tells you whether it worked.* | Column | What it tells you | | --------------- | ----------------------- | | **Source** | Who made the change | | **Action Type** | What changed | | **Status** | Whether it went through | Once you can read those 3 columns, no line in the log can stop an investigation. ## Sources — who did it | Source | Who that is | What triggers it | | --------------- | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Manual** | A named user | Somebody pressed **Send** on the [Yielding Board](/revhero-docs/setting-your-rates/yielding-board.md), edited [Pricing](/revhero-docs/setting-your-rates/pricing.md), or saved a configuration change | | **Integration** | A connected system | A sync ran with your property management system, your channel manager or RoomPulse | | **System** | Revhero itself | Routine background work, such as a nightly recalculation | A **sync** is the transfer of data between Revhero and a connected system. **Manual** lines carry a person's name. Every other Source carries a system label. You can therefore always tell whether a change was a human decision or an automatic action. ## Action types — what changed | Action type | What it covers | | ---------------- | ---------------------------------------------------------------------------------- | | **RATES** | Send-rate changes that were sent out | | **LOS** | Length-of-stay restrictions — minimum stay and maximum stay | | **STOP SALES** | Stop sales switched on or off for a room, a board or an occupancy combination | | **CLOSE OUT** | Close-out flags applied to specific stay dates | | **RMS** | Recommendation activity | | **POLICY** | Cancellation, no-show and deposit policy changes | | **COMMISSION** | Commission structure changes | | **SPO** | Special offers created, changed or switched off | | **VOUCHER** | Voucher creation, redemption flags and deactivation | | **CHANNEL** | Rate or availability changes for 1 specific channel | | **BOARD** | Board and meal-plan supplement changes | | **CAMPAIGN** | Marketing campaign tagging and activation | | **TOOLS** | Setting toggles switched on or off | | **SITUATION** | Free-text notes that somebody added to give a change context | | **AVAILABILITY** | Availability corrections. These are uncommon, and usually come from an integration | | **SYNC** | Sync activity with a connected system | People confuse **RATES** and **RMS** more than any other pair. **RATES** is the change made to a rate. **RMS** is the engine that produced the recommendation behind that change. **TOOLS** is almost always somebody switching a setting on or off. It is not a rate change. ## How a line ended A line records whether the change went through. If it did not, the line carries a reason in plain language, and that reason is what you act on. Read it, fix the cause in the system that refused the change, then send again. Some lines show the same value before and after. That means the send made no change to what your channel manager already held. Nothing is wrong. The line exists so the record is complete. ## Which fields you can rely on Before you build a report from a downloaded file, check which columns are always filled in. | Field | Always there? | Notes | | ----------------------- | -------------------------------- | ---------------------------------------------------------------------- | | Timestamp | Yes | Recorded against a single time zone throughout | | Source | Yes | 1 of the 3 values above | | Actor | Yes | A person's name for manual changes. A system label for everything else | | Action Type | Yes | 1 of the 16 values above. Never blank | | Status | Yes | Whether the change went through | | Stay date or period | When it applies | Rate changes and restriction changes only | | Room, board, occupancy | When it applies | These identify exactly what was affected | | Before and after values | When it applies | The change itself | | Reason | When a change did not go through | A plain-language explanation | ## 1 action can write 2 lines One user action that changes 2 different things produces 2 lines. If you send a rate and a minimum stay in 1 click, you get 1 **RATES** line and 1 **LOS** line. Each line has its own outcome, so 1 of them can go through while the other does not. ## Turning an audit request into a filter Knowing these values turns a vague audit request into an exact filter. For example, *"every change to commercial terms in the last quarter"* becomes POLICY, COMMISSION, SPO and VOUCHER over 3 months. [Filtering and search](/revhero-docs/automation/event-log/filtering-and-search.md) lists the combinations worth memorising. ## If something looks wrong | What you see | Usual cause | What to do | | ------------------------------------------ | --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | | The Source column shows a dash | An older imported line, where the source was not captured | Treat the source as unknown for audit purposes | | Before and after are empty on a RATES line | The send made no change | This is expected | | The Status column is blank | A send that has not been acknowledged yet | Refresh the page. If the column stays blank, check your integration status in [Settings](/revhero-docs/your-hotels-setup/settings.md) | | The reason on a failure is vague | Your channel manager returned a generic message | Open the send history under [Settings](/revhero-docs/your-hotels-setup/settings.md) for the fuller response | ## Related * [Event Log](/revhero-docs/automation/event-log.md) * [Filtering and search](/revhero-docs/automation/event-log/filtering-and-search.md) — putting these values to work * [Investigating a rate send](/revhero-docs/automation/event-log/investigating-a-rate-send.md) *** **Was this page helpful?** If something here is wrong, unclear or missing, email [support@revhero.com](mailto:support@revhero.com?subject=Manual%20feedback%20%5Ben%5D%20event-log%2Fevent-types.md) and quote this page: `event-log/event-types.md`. Say what you expected to find — that is the part we can fix.