Suddenly App Engine not Serving Anymore: Error code 123

[Karl-Heinz Müller]

I have a few app engines running, serving different domain names using the same application code php. 

Two of them suddenly stopped serving content. In the log file I see the following error message:

    I 12:56:46.855 This request caused a new process to be started for your application, and thus caused your application code to be loaded for the first time. This request may thus take longer and use more CPU than a typical request for your application.
    E 12:56:46.855 Process terminated because the request deadline was exceeded. (Error code 123)

I have another app engine running the same application without any issues and accessing the same data storage unit. Wondering why two shut down and the other not. 

No changes have been done. The incident started today 12:00

Thanks

[Michael (Cloud Platform Support)]

Hi Karl,

Are you still experiencing this issue? Does your two applications at all connect to CloudSQL instances in the us-central1 region?

Cheers!

[Karl-Heinz Müller]

Hi Michael,

Thank you for following up. Now, the problem has been resolved. The incident has taken place from around 12:15 till 13:30 but now the pages are served as usual.

Thank you

Karl-Heinz

[Tom Campbell]

I couldn't really afford this kind of outage when my app is deployed. is there a away around this, for example, having both a US and  EUR -based servers?

[Kaan Soral]

I also see some outages from my logs

The worst part is that the SLA refunds are not automatic, I have too many things on my plate and the SLA refund/request process is too criptic

[Michael Sander]

I've randomly started seeing these too. Did you do anything that worked?

[Kaan Soral]

Yes, manually slowing down the app almost diminishes these

But I still see 40-50 of them every now and then

[Michael Sander]

What do you mean slowing down the app? Lowering the taskqueue execution speed? Cron speed?