This error is rather generic and can be caused by multiple factors. Have you read past issues like this that have possible solutions? In this sample, the issue was solved through re-associating the App Engine service account with the app, for example. On a different occasion, it appears to be caused by transient network errors, are you still unable to deploy the version and are seeing the same error?
Otherwise, can you give more details about the changes that you added in the last deployment which failed? Confirming whether all your App Engine Flex quotas are under the limit would also be useful, which you can confirm by searching on the Cloud Audit logs for any quota exceeded errors.
The solution from the IssueTracker URL you were not able to access is also published in this Stackoverflow thread. You can try to check if it helps, but from the new error that you have received, it seems this is more of an issue related to the process of building your custom runtime on App Engine Flex.
How long is the build process taking? In case it’s more than the default of 10 minutes, you’d have to set a larger timeout, which can be done alternatively with this command: “gcloud config set app/cloud_build_timeout <TIMEOUT_SECS>”. Otherwise, doing a fresh build without using cached layers, could also help. You can use the “--no-cache” flag when running gcloud app deploy to test this out. Moreover, have you also seen any difference when allocating additional memory and CPU to your App Engine instance?