The actual timeout is higher than the ceiling, why not just ask the publisher to set an actual ceiling they are comfortable with?

Are you suggesting that pubs just set s2sConfig.timeout to be the same as what's sent in pbjs.requestBids() and use that as the ceiling?

I would solidly prefer not to have to (A) document that and (B) get existing pubs to change the page if/when they want to try this feature when it's easy and effective to get the client-side timeout.

from here:

If the s2sConfig timeout is greater than the Prebid.js timeout, the s2sConfig timeout will be automatically adjusted to 75% of the Prebid.js timeout in order to fit within the auction process.

AFAIK this has never been the case since at least my time with Prebid. Do we want to also implement something like it - maybe a fixed 500ms discount? (percentage doesn't make a lot of sense to me, if I increase client-side timeout it's not like the latency to server also increases).

this has never been the case since at least my time with Prebid

Hmm. Good topic. I think 500ms would be an overly large buffer. The number depends a lot on the user's network proximity to the nearest Prebid Server. Discuss in a future meeting?

Discussed. Agreed that a publisher should be able to define the tmaxmax like this:

pbjs.setConfig({
   ortb2: {
      ext: {
         tmaxmax: 888
      }
   }
});

The ortbConverter library should check for the existence of ext.tmaxmax and if not there, set it to the timeout value passed to requestBids()

@bretg I can also add that the below does not seem to be the working

If the s2sConfig timeout is greater than the Prebid.js timeout, the s2sConfig timeout will be automatically adjusted to 75% of the Prebid.js timeout in order to fit within the auction process.

Tried setting timeout in s2s to 9000 and timeout in requestbids is 600, but tmax is still 9000 in the request.

Thanks for confirming @bmjoju - fixed the docs page.

@bretg can you remind me, is Magnite picking this up?

Tried setting timeout in s2s to 9000 and timeout in requestbids is 600, but tmax is still 9000 in the request.

Should we track this as a different bug?

is Magnite picking this up?

Code for PBS-Java looking at tmaxmax is in QA.

Tried setting timeout in s2s to 9000 and timeout in requestbids is 600, but tmax is still 9000 in the request.

Not sure how that could be. @bmjoju - what version of PBJS are you running. The latest code in the ortbconverter does this:

request.tmax = s2sBidRequest.s2sConfig.timeout;

@bretg It is version v8.31.0. It was this in the documentation that didnt work and you also fixed the docs:

If the s2sConfig timeout is greater than the Prebid.js timeout, the s2sConfig timeout will be automatically adjusted to 75% of the Prebid.js timeout in order to fit within the auction process.

The tmax is working and set to what im setting timeout to in the s2sConfig. But the docs just said that the timeout in the s2sConfig config would be adjusted if set too high than the prebid.js timeout used in requestbids.