Skip to content
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

Timeout on page is different to the config. #8973

Closed
Jordanjscott opened this issue Sep 8, 2022 · 5 comments
Closed

Timeout on page is different to the config. #8973

Jordanjscott opened this issue Sep 8, 2022 · 5 comments

Comments

@Jordanjscott
Copy link

Type of issue

I have the Prebid timeout set in the config to 1500, the failsafe at 2000, and consent manager at 8000. When implemented on page however, the timeout is showing as 3000ms. There is no reference of 3000 anywhere in the code.

Description

Steps to reproduce

View config on the test page below.

Test page

https://www.thelondoneconomic.com/politics/ben-jerrys-send-pointed-message-to-new-home-secretary-334534/?pbjs_debug=true

Screenshot 2022-09-08 at 20 43 39

Screenshot 2022-09-08 at 20 29 35

@dgirardi
Copy link
Collaborator

dgirardi commented Sep 8, 2022

How are you using PREBID_TIMEOUT in your example? I can't find it in the test page config. To set bidder timeout to 1500 you want do pbjs.setConfig({bidderTimeout: 1500}).

I see that some of our examples (like this one) use timeout (instead of bidderTimeout) which I think is incorrect. But I don't see that in your test page either.

@dgirardi
Copy link
Collaborator

dgirardi commented Sep 8, 2022

And I should add - 3000 is the default for bidderTimeout, so it's behaving as if the timeout was not configured.

@dgirardi
Copy link
Collaborator

dgirardi commented Sep 8, 2022

Correction: if you are using the timeout argument of requestBids, it seems to be working as intended:

image

in your case the timeout is only for that specific auction, so getConfig() returns the default value.

@Jordanjscott
Copy link
Author

Correction: if you are using the timeout argument of requestBids, it seems to be working as intended:

image

in your case the timeout is only for that specific auction, so getConfig() returns the default value.

Thanks for the info @dgirardi. That's correct, i'm using requestBids function as I'm running parallel auctions with A9.

Could you explain what you mean by the timeout running only on the specific auction? The timeouts set should be running on every auction here. Or is it a case of the 1500ms being respected on page, but debugging not picking it up as it's handled via the requestBids function?

@dgirardi
Copy link
Collaborator

dgirardi commented Sep 9, 2022

if you call requestBids({timeout: ...}), the timeout applies only to that call/auction, and overrides the global setConfig({bidderTimeout: ...}). Conversely, the timeout argument is optional, and if omitted that auction will use the global bidderTimeout config. If you are only calling requestBids once then they are redundant.

Auction-specific arguments are not accessible via getConfig, but if you are looking for a confirmation you should be able to see them set correctly in auction events like auctionInit or auctionEnd.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

3 participants