how do I get my 'Recipients Emailed' quota back after hrd migration?

73 views
Skip to first unread message

Karl Rosaen

unread,
Mar 16, 2012, 11:14:11 AM3/16/12
to google-a...@googlegroups.com
Hi, I just migrated our app to the high replication datastore, billing enabled and everything.

I can't seem to adjust or opt in to pay more for the mail api quotas, and the default limit of 100 recipients emailed is not nearly enough and it's disrupting our application.

In our previous app, our quota for 'Recipients Emailed' was 1,771,789, I think I opted in to pay more for that limit a while back.

Anyways, how do I get my quota back? We're willing to pay!

Karl Rosaen

unread,
Mar 16, 2012, 11:22:09 AM3/16/12
to google-a...@googlegroups.com
Ok, I know see that the limit is 100 until "the first charge is cleared":


but given we just migrated an app, waiting for up to a week for the first charge to go through is not really acceptable... I'll try to file a production ticket about this, but I would hope that the migration tool, when used with an app in good standing, could transfer the email quotas to avoid disruption of sending emails.

Jose Montes de Oca

unread,
Mar 16, 2012, 11:21:41 PM3/16/12
to google-a...@googlegroups.com

Karl Rosaen

unread,
Mar 19, 2012, 9:56:14 AM3/19/12
to google-a...@googlegroups.com
Thanks Jose, that did the trick

Per

unread,
Mar 20, 2012, 9:43:17 AM3/20/12
to google-a...@googlegroups.com


Hi Jose, thanks for that link.

I just did the migration to HRD, and it was not at all obvious to me that this limit gets re-introduced despite having been a paying GAE user for a year now. The migration guide says to "update billing", which I did. A link to the URL mentioned by Jose would have been very helpful. How about placing that link into http://code.google.com/appengine/docs/adminconsole/migration.html ?

Cheers,
Per

Jose Montes de Oca

unread,
Mar 20, 2012, 12:10:13 PM3/20/12
to google-a...@googlegroups.com
Per,

Thanks for the valuable feedback! I'll forward this to the team so we can add this to our migration documentation to avoid this issue in the near future.

Best,
Jose
Reply all
Reply to author
Forward
0 new messages