1. Live Booking Notification (LNM) - This is triggered immediately and means that data is updated in real time, however in some instances this may fail to trigger.
Failed notifications (those which for RU do not get HTTP 200 response within 3 seconds)
are scheduled for delivery later. The LNM will try do deliver the notification around three times.
First time immediately, then around 2 minutes later. If failed, around 8 minutes later. If failed,
around 18 minutes later.
2. Pull Reservations - Runs Every Hour - Fail safe feature if the LNM fails to fire correctly
This will run automatically every hour and pulls down any bookings that were made within the last 2 hours, this ensures that your availability in the worst case scenario is up to date within the last 60 minutes.
3. Reservations - You can also pull reservations from within the property, this is required if an error occured on step 2
If you have just activated the connection and there are double bookings, you will need to manually correct until you can successfully pull all bookings into iPro.
Using the feature "Pull Reservations From Specific Start Date", you can pull down 7 days worth of bookings. So if I set the date to the 2017-05-01, it will pull down all bookings made between the 1st to 8th May. I would repeat this for each week until I have all bookings for that property.
Now run "Push Availability", you should receive the message - "Availability push was successful"
Then run "Pull & Push Availability", you should receive the message "Availability pull and push was successful"
Once you have received this message you can be confident that the property is syncing correctly.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article