41–50 of 119 posts
I wonder if people at Google know how awful it is to report an Appengine bug. You have to battle for days to get your bug acknowledged. I've noticed that they've added more support people since the early days but it's still a pain as they seem to have an incentive to answer the tickets as fast as possible without doing any real investigation. The linked issue is a good example of this behavior.
Sendgrid is a great alternative and not hard to set up.
Earlier quoted context omitted.
They should be working on a migration tool for users of AppEngine to migrate to Google Container Engine.
We wouldn't use it. To me, the whole point of Appengine is to abstract out system administration. GCE (like AWS) abstracts out the systems, but not the administration - you suddenly become responsible for all the scaling, fault-tolerance, and all the subsystems that Appengine manages for you.
Earlier quoted context omitted.
They should be working on a migration tool for users of AppEngine to migrate to Google Container Engine.
We wouldn't use it. To me, the whole point of Appengine is to abstract out system administration. GCE (like AWS) abstracts out the systems, but not the administration - you suddenly become responsible for all the scaling, fault-tolerance, and all the subsystems that Appengine manages for you.
I've tried Containers with Google App Engine Flexible Environment (in beta now) and liked that it's much more customizable than standard GAE. Basically, you just need any Docker container listening on port 8080. But deploy time took 10-20 minutes, so I'm still preferring Standard. Hopefully they'll fix that before GA release.
Reading through the thread, it looks like in the last few days it's been narrowed down to "messages which contain the URL of the App Engine instance silently disappear with no bounces or errors."
And only sometimes. The issue resolved itself on my app two weeks ago. My guess is there is an outgoing spam filter run amok in some of the clusters.
http://penguindreams.org/blog/how-google-and-microsoft-made-...
I have seen more phishing/ransomware e-mails come through mine (lots of malicious Javascript made to look like Excel files), so I can understand how great the risk is. The fact still remains though. E-mail is broken and is less reliable than an envelop dropped in a letterbox.
At least a few reported that it was bouncing at the destination once they set up an appropriate handler. They are only "not being sent" when there is a url in the message and that is a big red flag on the receiving side (not much text but a url). It doesn't look like an App Engine problem. It looks like messages being identified as spam problem.
Not the case for me. No bounces being reported. In any case, gmail and outlook don't bounce messages for spam; They put them in the spam bin. Nothing whatsoever changed in my code. I haven't touched it in a year, and all of sudden email stopped on the 1st of April. There's nothing in the changelogs to indicate there was a change that should cause this behaviour. It's absolutely an App Engine problem. https://cloud.go…
I wonder if people at Google know how awful it is to report an Appengine bug. You have to battle for days to get your bug acknowledged. I've noticed that they've added more support people since the early days but it's still a pain as they seem to have an incentive to answer the tickets as fast as possible without doing any real investigation. The linked issue is a good example of this behavior.
I wonder if people at Google know how awful it is to report... No. (Or they don't care.)
At least a few reported that it was bouncing at the destination once they set up an appropriate handler. They are only "not being sent" when there is a url in the message and that is a big red flag on the receiving side (not much text but a url). It doesn't look like an App Engine problem. It looks like messages being identified as spam problem.
I'm pretty surprised by the long wait times between "updates" from support... that's pretty rough. I understand it can be hard to get a good signal to noise ratio with support, but when so many other people are reporting issues, perhaps it's time to take it a bit more seriously? This thread is a great example of why support is so hard.
If my customers don't get a reply within a few hours, then all hell breaks loose. Even if, there request comes in at 3am / 0300 on a Sunday morning my time.
To be fair, when I point this out to them they do apologise, didn't realise time difference, are in a different part of the world where Sunday is not a day off etc. I then ask what they expect from some billion dollar companies support wise and they say they are happy with a reply within a week. Asking them why a one man shop doing quite a bit less than billions of dollars is expected to provide so much more.
Anyway, rant over. Support isn't hard. You hire enough competent people as your customers require. The end. Happy customers