Timeouts

  1. What's the required timeout at...: All the timeout settings can usually be customised if needed and more often than not the timeout is provided by the clients directly via XML (sometimes this aspect is referred to as dynamic timeout), so we cannot do anything on that (cannot change, cannot know in advance). So for questions about timeout, it's always a good practice to advise that we provide a default number but it can be adjusted and ruled outside the scope of the TOWeRS system.

  2. ...search step: At search step we have a couple of timeouts:

    • for single hotel searches, it's usually good to have 9 seconds
    • for multi-hotel or destination it's usually a good choice to stay around 20 seconds.
  3. ...evaluate step: Despite the fact that usually this part of the flow is fast, within a few seconds, the system can wait up to one minute to be completed. The recommended timeout, if required, is 15 seconds.

  4. ...booking step: The system technically wait up to 5 minutes to get a booking response but clients of the system can be configured to automatically cancel reservations taking longer than 1 minute or so. This thing should always be stressed giving 1 minute as preferred choice.