Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
 

...

Why am I receiving a 'Throttle limit reached, please try again later...' message?

You have breached the throttle limit that is placed on all our pmsXchange V2 connections. There are 3 breaches that will generate this response:

...

Note
SOAP Fault - High Server Load


What are the throttle parameters I need to work within?

Request per minute throttle = 40 

Messages per request (message size) = 500 messages

Concurrent requests Limit = 3

NOTE: These throttle parameters are what you'll have when you go through our certification process, and will be the initial throttle parameters you initially have in production. These parameters can be tweaked in consultation with our Application Operations team as the number of hotels you have grows. You'll be given contact details for the Application Operations team once you are certified and live in production.


Do I need to send 'Delta' updates to pmsXchange when a change is made in my pmsXchange connected integration?

Yes, it is extremely important that you only push 'Delta' changes to pmsXchange. Full refreshes are only allowable a maximum of once per day. Many throttling breaches are to due large requests being sent, even though only small amounts of data have changed in the upstream integration.

...

It is very important to ensure that you have measures in place to handle throttling. If you receive a 'Soap Fault' response advising your integration has been throttled, it is important that the situation can be flagged and action taken by your application/infrastructure support teams. After throttling occurs, it is important that your team takes immediate action to correct the cause of the throttle breach. Our application support Application Operations teams can work with your technical teams to come a solution.

...