Why Do My GCP Cloud Functions Show \'Function Execution Took X Ms. Finished with Status: Response Error\' for Non-200 HTTP Codes?

Troubleshooting GCP Logs Displaying "Function Execution Took X Ms. Finished with Status: Response Error" for Non-200 HTTP Codes

Google Cloud Platform (GCP) Functions recently encountered an issue where non-200 HTTP response headers resulted in "Function Execution Took X Ms. Finished with Status: Response Error" logs. Despite attempts to recreate the issue with a minimalistic function returning various HTTP codes, the error persisted.

Explanation

Unfortunately, this issue was caused by an internal problem within Google's infrastructure. It affected all GCP Functions that deviated from the default 200 status code.

Resolution

Fortunately, the issue has been resolved with the latest Google software update on May 17, 2022. Cloud Functions should now behave as expected, handling non-200 status codes without triggering the error message.

Legacy Issues

If you continue to experience the error, it is recommended to contact Google support through either issuetracker.google.com/issues/... or by raising a support case.

The above is the detailed content of Why Do My GCP Cloud Functions Show \'Function Execution Took X Ms. Finished with Status: Response Error\' for Non-200 HTTP Codes?. For more information, please follow other related articles on the PHP Chinese website!