Details
-
Type: Bug
-
Status: Open
-
Priority: Major
-
Resolution: Unresolved
-
Affects Version/s: Gooseberry
-
Fix Version/s: All Time Backlog
-
Component/s: Budget Estimate Service
-
Labels:None
-
Environment:
Google JP Environment
AML SAPI Final - Build 1092
AML Core Final - Build 378
Bid Manager Final - Build 913
-
Story Points:8
Description
Steps:
1. Login to Reseller UI (Google JP)
2.Create a Merchant and select large number of BAs (>15) with location as Country
3.Click on Add a Quote
Actual Result:
It sends BES request for estimates - after retrying it fails. UI shows
CA$0.00 - CA$0.00 although for each BA/BL shows quote range.
(Please see the attached screenshot)
Snippet of Jboss log:
14:42:18,806 DEBUG [GoogleTrafficEstimator] Exception found on TrafficEstimatorThread 1
AxisFault
faultCode:
Server
faultSubcode:
faultString: [RateExceededError <rateName=RATE_LIMIT, rateKey=null, rateScope=ACCOUNT, retryAfterSeconds=30>]
faultActor:
faultNode:
faultDetail:
ApiExceptionFault:<ns2:message>[RateExceededError <rateName=RATE_LIMIT, rateKey=null, rateScope=ACCOUNT, retryAfterSeconds=30>]</ns2:message><ns2:ApplicationException.Type>ApiException</ns2:ApplicationException.Type><ns2:errors xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns2:RateExceededError"><ns2:fieldPath/><ns2:trigger/><ns2:errorString>RateExceededError.RATE_EXCEEDED</ns2:errorString><ns2:ApiError.Type>RateExceededError</ns2:ApiError.Type><ns2:reason>RATE_EXCEEDED</ns2:reason><ns2:rateName>RATE_LIMIT</ns2:rateName><ns2:rateScope>ACCOUNT</ns2:rateScope><ns2:retryAfterSeconds>30</ns2:retryAfterSeconds></ns2:errors>
[RateExceededError <rateName=RATE_LIMIT, rateKey=null, rateScope=ACCOUNT, retryAfterSeconds=30>]
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
Tomcat log attached
Expected:
SAPI already returns an UNAVAILABLE estimate status when this happens. One solution could be a pop up that says something like "Budget estimates are currently unavailable for one or more business areas and locations" every time the SAPI response includes an UNAVAILABLE status.
This behavior should not stop the user from deploying an order. Campaigns should not become unsellable when estimates aren't available.
BES has 5 retries before giving up. We do not want to retry continuously until an estimate is retrieved.