Bidding Agent and Augmentor Response Codes

For customers who deploy a Bidding Agent or Augmentor, Beeswax will provide real-time monitoring metrics within the Buzz UI. Below you can find a list of common statuses along with their associated descriptions.

200Success. Note: the response could still be malformed, so it's always good to confirm with your Beeswax Solutions Consultant by supplying a human readable bid/augmentor response)
204Empty response. Present when a bidding agent/augmentor decides not to bid.
400Bad Request. Typically means the bidding agent/augmentor endpoint is an invalid URL. If any DNS changes were recently made, please notify your Beeswax representative to force new DNS lookup.
502Bad Gateway - Normally due to some issue within customer bidding agent/augmentor (e.g. improper parsing of the bid request).
MaxConnectsThe number of requests that have encountered a bidding agent/augmentor with no available connections.
TimeoutBid/augmentor response latency exceeds max timeout set by Beeswax (default timeout value is 10ms).
CanceledCanceled connection attempts by Beeswax. This is generally 1:1 with timeouts; however, if your server is not set up for "Keep connection open" then this will equal the number of timeouts + 200s + 204s
DroppedResponses that are ignored by your Beeswax Stinger (bidder) instance, typically due to Beeswax throttling following response latency. Beeswax default throttling rules will drop 80% of traffic when the percentage of timeout responses are greater than 5% over a 5 minute period.
No Eligible CandidateIndicates the volume of traffic that is not getting passed to a bidding agent because no line item with matching traffic is using that agent's respective custom bidding strategy. When prefixed with "Hexbid", this can always be ignored as “Hexbid” is the Beeswax internal bidding agent.
Traffic FilteredIndicates how much traffic is being manually filtered from a Bidding Agent. Please contact your Beeswax representative to address this case.