What is the Activity Log?
The Activity Log gives you full visibility into every calendar operation across your listings. Every time a price is changed, availability is updated, a reservation is synced, or a channel push is triggered, the Activity Log records it with details about who made the change, when, and whether it was successfully synced to all channels.
Use the Activity Log to:
Audit changes — see who changed what, when, and from where
Monitor channel sync — verify that updates reached all connected channels
Identify errors — spot failed syncs before they cause overbookings or pricing issues
Retry or dismiss — re-queue failed operations or acknowledge resolved errors
Prerequisites
Calendar Service v2 must be active on your account
The Activity Log permission must be enabled for your user role
Accessing the Activity Log
There are several ways to access the Activity Log:
Per-Listing Activity Log
Open any listing and click Activity Log in the sidebar. This shows all activity for that specific listing, including calendar updates, reservation syncs, and channel push results.
Global Activity Log (Channel Sync Activity)
Navigate to the Channel Sync Activity page from the main menu. This shows activity across all your listings in one view, making it easy to spot issues across your portfolio.
Multi-Calendar Sync Status
The Multi-Calendar shows a sync status indicator in the toolbar that summarizes the health of all your listings. It also displays colored dots next to individual listing names to flag sync issues:
Green dot — all synced, no issues
Amber dot (pulsing) — sync jobs in progress
Red dot — sync errors that need attention
Click the sync status indicator or any listing dot to go to the Activity Log.
Activity Types
The Activity Log tracks the following types of operations:
Activity | Description |
Calendar Update | A single-range calendar change: price, availability, min stay, notes, CTA/CTD, LOS, or booking value |
Bulk Calendar Update | Multiple calendar changes applied at once (e.g., from a pricing tool or bulk edit) |
Reservation Sync | A reservation was created or updated in the calendar |
Reservation Removed | A reservation was cancelled or removed from the calendar |
Reservation Moved | A reservation was moved to a different listing |
Listing Sync | Listing details or channel integration settings were synced |
Full Sync | A full calendar push was triggered for all connected channels |
What Each Entry Shows
Every activity log entry includes:
Timestamp — when the operation started
Activity type — what kind of operation (see table above)
Listing — which listing was affected
User — who made the change (or "System" for automated operations)
Source — whether the change was made from the web interface, mobile app, or API
Duration — how long the sync took to complete
Status — current sync status (see below)
Expanded Details
Click any entry to expand it and see:
Calendar data preview — the date range, prices, availability status, and other changes applied
Channel sync jobs — per-channel breakdown showing which channels received the update, how long each took, and any errors
Bulk data preview — for bulk updates, see the full set of changes that were applied
Error details — specific error messages from failed channel syncs
Sync Statuses
Status | Meaning |
Synced | The change was successfully applied and synced to all connected channels |
In Progress | The change has been applied and is being synced to channels |
Error | One or more channel syncs failed — action may be required |
Dismissed | An error that has been acknowledged and muted by a user |
Filtering & Searching
Use the filters at the top of the Activity Log to narrow results:
Date range — filter by start and end date (default: last 30 days for per-listing, last 2 days for global)
Activity type — show only specific operation types
Status — filter by sync status (synced, in progress, error, dismissed)
Listing — in the global view, filter by a specific listing
The status summary bar at the top shows counts for each status. Click any status badge to quickly filter by that status.
Actions: Retry & Dismiss
Retry Sync
When a channel sync fails, you can retry it directly from the Activity Log:
Expand the failed entry
Click Retry Sync
The system queues a new sync job for the affected listing and channels
The original error entry is automatically muted, and a new entry is created for the retry attempt.
Retryable activity types: Calendar Update, Bulk Calendar Update, Listing Sync, Full Sync, Reservation Sync, and Reservation Removed.
Dismiss Errors
If an error has been resolved externally or is no longer relevant, you can dismiss it:
Expand the error entry
Click Dismiss
The entry's status changes to "Dismissed" and it no longer appears in error counts
Dismissed entries remain visible in the log with a "Dismissed" badge for audit purposes.
Automatic Error Resolution
The system automatically checks whether errors from bulk operations actually affected each specific listing. If a bulk update reported an error but the individual listing's channel jobs all succeeded, the Activity Log automatically resolves that listing's status to "Synced". This reduces false error alerts from large batch operations.
Channel Sync Details
When you expand an activity entry, the Channel Sync section shows per-channel breakdown:
Channel name and logo — which channel received the update
Communication time — how long the channel API call took
Status — success or failure for each channel
Error details — specific error messages from the channel (if any)
Request data — preview of what was sent to the channel (date ranges, prices, availability)
This level of detail helps you quickly identify whether an issue is on your side or the channel's side.
Common Errors and Their Meaning
Cannot create derived prices for LOS pricing model rate - This indicates that the property on Booking.com or Airbnb is using a different pricing model. This is a genuine issue and should be investigated further, so please contact a member of the team for assistance.
No calendar data for {Unit_Id} - Around 99% of these cases are caused by multi-unit listings. This occurs because we only send calendar data for the main (leading) listing, while related listings do not receive this data, which results in an error. We are currently working on a fix to prevent this error from being displayed. To assess the situation, first check whether the listing is part of a multi-unit setup. If it is, this behavior is expected and not considered an issue. If it is not, then the problem is likely related to the rate configuration, and you should contact a member of the team for further investigation.
Unfortunately, a server error prevented your request from being completed - This error can occur if Airbnb is undergoing maintenance or if your connection timed out. The message “Request failed with status code 500” indicates a server-side issue, meaning the channel experienced a temporary problem and rejected the request we sent. We automatically retry these requests, so in most cases the subsequent attempt is successful. This is not considered an actual issue. You can also verify this by checking whether the latest requests for the listing have been completed successfully.
The request could not be authenticated - This indicates an issue with the channel account. Identify which specific account the request failed for and verify whether the onboarding process has been completed. If onboarding is complete, please contact the team to investigate the problem with the channel account.
Failed to update listing integrations: error add listing integration - This is error with the listing relation, one of the listings has problem, you should check all listings from that message and see if all are successfully connected in the Parent-Child relation. Its not an actual issue, it happens with some inactive listings, if everything is okay than contact us for investigation.
Occupancy should be positive, different than leading_occupancy, and lower than the room's capacity - This is common Booking.com rate issue, Booking.com is not allowing the leading occupancy of a rate to be equal or more than the room capacity. This must be fixed from the client side.
You do not have permission to access this resource - This indicates an issue with the account. Please verify whether the affected channel property is properly connected to Hostify by checking the specific property where the request failed.
Rate does not belong to room - For Booking.com you need to check the mapping the rate with the room.
Unable to process JSON - This is happening for Airbnb, it is NOT an issue. We retry this requests and it is successful.
FAQ
How far back does the Activity Log go?
The Activity Log stores data indefinitely. The default view shows the last 30 days (per-listing) or last 2 days (global), but you can adjust the date range to see older entries.
Who can see the Activity Log?
Users with the Activity Log permission enabled for their role, and all staff/admin users.
What does "Auto retry failed" mean?
If the system attempted an automatic retry but it also failed, the entry shows "Auto retry failed — user action required!" You should review the error and either fix the underlying issue or retry manually.
Can I export the Activity Log?
The Activity Log is currently viewable in the application only. For data export needs, contact the Hostify support team.
Do dismissed errors affect sync status?
No. Once dismissed, errors no longer count toward the error totals shown in the Multi-Calendar sync indicators or the global status bar.