Warming up a disposable service instance incurs Google charges

[mwpowellhtx]

Hello,

I have reason to believe that warming up a service instance through your adpater may incur Google charges.

I've got a scenario in which I did not think I was hitting the service that hard, but the charges seemed excessive to me. In my unit test scenario I swapped out the actual request invocation for a unit test callback in order to simulate that aspect, but it did involve a "live" service instance, so hence my concern with that.

Can you clarify one way or the other the nature of the service connection and whether that does indeed incur charges?

Thanks!