That typically means your app returned a 500 error code to whatever was
fetching the document (it's not clear below whether you're running in a
browser or making an API call from an app or something else).
You should check the admin console for the deployed app and go to the logs
section. Any
I think I know what's happening now, so I'm sharing it for everyone's
benefit. I was using the feedparser library to parse a feed, and that got
into some sort of infinite loop. What worries me, though, is the fact that
the App Engine didn't log any information from any of the logging.info()
I might have more information after a lot of testing. It seems that if an
internal error happens while processing the request on the App Engine, then
that process is killed and none of the log messages are recorded. Can
someone from Google confirm this?
That might explain why I don't see any of
Hi Waleed,
You are not seeing any errors/warnings in the logs? There are a few
possibilities here.
If the request hits your app:
* You could be hitting the 30 seconds limit (maybe because the input
is too large or something). You should see an error in the logs.
* Your code could also be
Hi Mark,
I'm testing this on my dev app, which has no load at all, so it's not
the simultaneous requests limit. Although the same problem happens on the
production app for that specific request. It's a reproducible problem. This
is what I see in the logs:
03-02 04:42PM 08.454