-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong auctionDelay behavior in realTimeData module #8139
Labels
Comments
I believe this is a problem with the IAS rtd module, introduced in #7431 (@raguilar-ias can you verify?). Prebid.js/modules/iasRtdProvider.js Lines 140 to 150 in 887f703
|
I can confirm that we're looking into it on the IAS side. |
@rbarbini-ias ty! |
9 tasks
Repository owner
moved this from Tracking
to Done
in Prebid.js Tactical Issues table
Mar 31, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Type of issue
auctionDelay in realTimeData behaviour isn't correct
Description
As per doc, auctionDelay should be an upper limit that RTD will wait for module with waitForIt at true for a response, but this is not the case.
Its managed as a fixed time the RTD will wait, also if the modules get the response before.
Steps to reproduce
set the following config for RTD:
realTimeData = { auctionDelay: 50000, dataProviders: [ { name: "ias", waitForIt: true, params: { pubId: "929966" } } ] }
set bidders timeout to 10000 and make a call.
Prebid will make IAS RTD module call, IAS give response after around 150ms, RTD module will wait for 50 seconds, after 10 seconds prebid will trigger timeout.
Expected results
RTD IAS module will make call, after having the response bidders start make request without waiting the 50sec auctionDelay.
Actual results
Platform details
Tested with Prebid v5.20.2 and v6.13.0
The text was updated successfully, but these errors were encountered: