Availability Search paging specifications are incorrect

[HiroyukiNIshimura]

According to the specification, NextResultReference will be returned when there is a next page, but after NextResultReference is returned, the error object will be code 3051 (No more later flights.).
Further requests in that NextResultReference will return the code 2460 (A bad availability specification was found.) In the Error object.

Further requests with that NextResultReference will repeat code 2460 forever.

I think the expectation is that the Error object will not respond to the NextResultReference instead of the code 3051 (No more later flights.). Is there something different?

    <air:AvailabilitySearchRsp TraceId="zocUEWr1UYjKlsd_dsVxUHkJzQEF55ka_X4mPfpV" TransactionId="5A0951B80A0D6A7EF38B4994A1B8BED7" ResponseTime="1692" DistanceUnits="MI" xmlns:air="http://www.travelport.com/schema/air_v51_0" xmlns:common_v51_0="http://www.travelport.com/schema/common_v51_0">
      <common_v51_0:ResponseMessage Code="3051" Type="Warning">No more later flights.</common_v51_0:ResponseMessage>
      <common_v51_0:ResponseMessage Code="3051" Type="Error">No more later flights.| Origin:DEN Destination:LAX PreferredTime:2021-12-13 00:00 EarliestTime:2021-12-12 22:00 LatestTime:2021-12-13 04:00</common_v51_0:ResponseMessage>
      <common_v51_0:NextResultReference>H4sIAAAAAAAAAJ1UTWwTRxR+dmII4Dbip1EVBLRqRRASu2ad2OuGCyVplGpJIhwh5CiHiXe8mbDeWWbHyaZqkeCCOPTaiko9IVCRODS3SpUqemqOCHErHBBH1EtvOYU343WcbSgR7GF25s33vve9n92H/0AuEnB4iSwToyWZb5wXgqw6LJLxjSfH7vxFfu6BzCT0RuwbGocAkF3pVSs6nanzpuFZ0QqT9UXDcyODuCSUVEQG3jR5YIzHUpC6nOVXaeDc/PsE2zx4Pwt9c3CACDHLmlTFkXB2zkEHs0NlIlWTu9Q32zSmQlZDWmcNVieS8WAUGVwadhkquzB85dOYLfh0J5OjmCLJAn2UcMhRpTB9EnhmVQoWeAjJeYK3QgmHt11OBpJ6VODtviYXVOd4Da5DzoE9XDCPdU75UPBl5lJxARUltpzcgsdhSyQVSBVT6+8Ucqfue59cfvzHj+XvswC6LYAslV1Y/r8KT3+f/+LorZfzHbYMtrf0flzQfjJZyDjQH1Ei6ot6DsbIaiTBeHujqmn8aCzAeLfKdOP31mCARTOCNqigrgJOcTnBlnEW4YNQmxO7hM/SshI16oMwx4jUWWKn81ESSZ1V9/qx+xL3l3AikOXU7nOskaNYZKzwp6nMkoT0R9iJ2U1mTw3yLlo7KdSgnwXLxGc6gRoPaA0+5I1GRGUXkpeppPuWuEsUtYSPHS48U51NhUklKRPCKdJOMrc1EgPoZCgnQ2G2VP52LnaX5p5vqOkRcCINWiARNb7EpYPe3Nx4MT1v3M1C9mvYyy4y32cRfobswqLgAfe5typh8D/6uneqdpD5bm1gXZVwKB2srmHGZHW66/B5VbYWHqwfbFwrzwz1qAGPdojsaFNpa/x9M/PTt9bgS41f2Qd7x2XdnLg4G8ehcj+560zqPnfb14N1xdH2Gf5rtg3Pfh8DpyzpwdRGFKzehxSV3n2kCvDrL69AHQbfeLv2783kVq1H8N/V45y/gq/jxYJVKBesYrFiD5ctuzJsW4UR20bT8MiIhbix8amwzZltqbVP/13Ubr8eA7XLw1bQTDfoo9vPkqBt/2NvUvbo6OZbdP9Jf9im+3SY6NG6i4VSwSpbFds6axdL+BRKdgnVl4t2MckvjF8D5pNZY9EGAAA=</common_v51_0:NextResultReference>

[RicOsiro]

Hi,

as mentioned in the another issue the ideal analysis should be on the request and response message, sometimes on the entire worklow.
The API works according to the specification documented on the help pages. Some different response could return depending on the context. On non-production environment, the response is sometimes inconsistent due to internal restrictions or invalid data on any internal components. Also, the response could change if the client applications doesn't send the right message, a parameter was changed or even the session was expired. Also, some simultaneous operations with another test.
Please, could you test the NextResultReference on different routes, dates, PTCs, etc. If it is failing for all request/response it could be an environment error, please open a ticket on MyTravelport (https://my.travelport.com) to fix it.

thanks and regards

[HiroyukiNIshimura]

Thank you, RicOsiro!

Make sure to open a ticket on My Travelport.

Keep this issue open until you get a clear answer on MyTravelport.

[RicOsiro]

Hi,

the most important action is, to calling availability with different parameters because if you receive the response with NextResultReference as expected; no other action is needed also the ticket on my travelport.

thanks and regards