Cloud run returning status code 502 in 30 min to user's request but is finishing with status 200

[claudiocesar]

I'm experiencing problems with cloud run that has more than 30 minutes of execution. It is executing OK, but is returning for user 502 code when it pass 30 minutes.
My timeout request is 3600 seconds, but my quest is finished in 30 min with status code 502.

Some configurations of cloud run:

Concurrency: 3

Request timeout: 3600 seconds

CPU limit: 1

Memory limit: 2GiB

[henriquediog]

I'm experiencing the exact same problem. 

[camiloscd]

I'm facing the same problem since August 5th.

[mmizokami]

I am also having the same problem since the 2nd of August.

I saw that on August 3rd there was a new release of Cloud Run related to Load Balancing. I suspect it might have something to do with it.

[dmartins]

I'm facing the same problem and have opened the issue: https://issuetracker.google.com/issues/295457456

[claudiocesar · Accepted solution]

This problem has been resolved today. I've tested 2 cloud runs and they are working now.

[LuizHRGomes]

@claudiocesar How did you solve the problem?

[claudiocesar]

Hi Luiz, after some days the problem has gone and today is working fine.