Skip to main content

[Channel] What to Check When You Receive a Sync Error Notification (Temporary Errors)

H
Written by Hanai M

[ Overview ]

When a temporary error occurs while synchronizing with an OTA, you may receive notifications such as "Sync Bookings Error", "Sync Price Error", or "Sync Allotment Error". This article explains how to check these notifications and which cases require action.


[ Details ]

What is a temporary sync error?

A sync error notification is sent when, for example, communication with the OTA's server temporarily fails. Examples of these errors include:

  • HttpAdapterConnectionError

  • 99101 internal server error / Receive timeout

  • Failed to initialize browser

When a sync fails, AirHost automatically reconnects and retries the sync. If the sync completes successfully a few seconds to a few minutes later, the sync is not failing continuously and no action is required on your side.

You normally do not need to manually refresh the channel in response to a temporary error notification. A manual refresh is for re-importing information from the OTA when it has not been imported into AirHost.


How to check the sync status

Go to [Admin Console] ≫ [Property List] ≫ the relevant property ≫ [Channel Manager] ≫ [Settings], then open [Log] from the menu of the relevant channel. You can see the sync history, including when the error occurred and when the sync later completed successfully.

*The page linked from [View Details] in the notification email may not show where the error occurred.


Cases that require action

In the following cases, the error may not be temporary:

  • The same error keeps occurring and subsequent syncs are not succeeding

  • Reservations are not being imported, or inventory and rates are not reflected on the OTA

If "update allotments ignored - no inventory forms found" keeps appearing

If this error continues while inventory sync is turned on, settings changed on the OTA side may not have been imported into AirHost. Go to [Admin Console] ≫ [Channels] and refresh the relevant channel (this deletes old data and re-imports it).

If the error recurs after refreshing, or if any of the cases above apply, please contact support with the error notification details, the property and channel names, and a screenshot of the log.

Did this answer your question?