Campaign deployment failure with no enough budget even though the nominal budget is greater than the minimum price recommended by BES

Customer ID: 94542373000155-0414015935
TSA account ID is: 826

The campaign deployment failed with the following error.
reason=RangeError.TOO_LOW, field=operations[53].operand.budget.amount

Google did not deploy these campaigns because there wasn’t enough budget.

Looking at thee BES soap request Optus made and the response sent by TSA, the minimum price as recommended by google it is: 55.876

Looking at the nominal budget tables, the nominal monthly budget for this account is set at 64.35
Optus are also passing in as the monthly budget of 64.35.

As expected this matches the value for the monthly budget in the admaxNominalMonthlyBudgets table.

What was interesting was the budget estimate request was made in early November and Optus tried to deploy the campaigns for this account on the 27th of November.

It looks like google changed the minimum and maximum pricing for the BA/BL combinations.

The minimum Price as of 30th November for the BA/BL combinations for this account is: 62.538
The minimum Price early November for the BA/BL combinations for this account was: 55.876

So these values have changed.

But minimum Price is still few dollars (around 2 dollars) behind the budget optus is setting for this customer per month which is 64.35.

This account has a large number of site campaigns around 170.

Even though TSA hadn’t anticipated hundreds upon hundreds of campaigns with small budgets, we still shouldn’t error out. This should be considered a bug – as after a few days, the individual campaign budgets will accumulate higher than a penny and then we should be seeking to spend them.