Hi everyone Recently I had a very absurd experience with my old app, a cron didn't execute for 4 days, and after some changes and a new deployment, continued functioning as it should
Now I have a new problem with my new app, a deferred.defer task is fired, however it isn't executed, by looking at my internal metrics, this have probably happened numerous times, now that I started investigating it, I'm sure it will never happen again One shortcoming that makes it almost impossible to debug is the "Logs" system, the old version of "Logs" can't search the old logs, that part is obvious, the new version of the "Logs" UI/system is sluggish, however it does find things among the Logs / is able to search old logs, so that's good, my log cap is 400gb's by the way, and the logs are at 23gb's (not overflowed yet) - so I'm not missing any logs I've tracked the task which fired 2 deferred tasks (the task is a deferred task itself), I see that they both had the same task name (they shouldn't, it's fixed now) so one of the tasks resulted in a TaskAlreadyExistsError - however - the initial task didn't execute either - I'm wondering whether there could be a bug which causes the originally task to be blocked in case of a TaskAlreadyExistsError (all my tasks have unique task names to ensure a task doesn't get executed twice, however I see/verify that the initial deferred.defer didn't result in an exception) *Long story short*, an important deferred task didn't execute, I don't know why, all my taskqueues have ridiculous retry routines to ensure everything gets executed Any ideas? -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
