App Engine did have an issue which caused additional Datastore operations for some apps between 11/19/14 16:26 and 11/21/14 03:03 PST. The additional operations may have resulted in your app creating tasks that were executed after the incident was resolved.
If you believe that you were affected, you should contact us using the instructions here: https://support.google.com/cloud/answer/3420056 On Sunday, November 30, 2014 5:25:16 AM UTC-8, Kaan Soral wrote: > > I've inspected my new app, that doesn't have much logs, so it's easy to > inspect (since the app doesn't have much traffic, there was no noticeable > increase in costs/usage) > > On that app, the issue occurred around: 2014-11-22 10:20:00 UTC (end date) > exactly, for 5 hours, both internal and external imports failed, one > example is jinja2 that AppEngine provides, I'm able to prove this from the > logs > > So for anyone that's reading this, it's probably a good idea to > repeat/mend all actions around (2014-11-19/2014-11-22) > > For this app, the instances were using 1.9.16 when the issues occurred, so > it doesn't support my 1.9.16/1.9.17 theory > > I'm guessing by repeating the daily actions 3 times with 8 hour intervals, > I managed to prevent damage to this app, however I've obviously lost a lot > of time and energy > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
