Google Cloud Functions timeout limit changes

I have a Google Cloud function that was working for the last weeks. I removed it and try to deploy, getting this error:

> INVALID_ARGUMENT: The timeout for functions with an event trigger cannot exceed 540 seconds.

This was the command used to deploy and update (and it was working until today):

gcloud functions deploy import-XXXXXXX-function \
--gen2 \
--runtime=go119 \
--memory=128Mi \
--timeout=t30m \
--region=$REGION \
--source="$ROOT" \
--entry-point=ImportXXXXXXX \
--trigger-event-filters="type=google.cloud.storage.object.v1.finalized" \
--trigger-event-filters="bucket=$BUCKET" \
--set-env-vars=STAGE=$STAGE

I can see that the documentation was updated days ago (Last updated 2023-02-02 UTC.) and now the max timeout for event-driven functions is 540 seconds.

So two question:

1. My job is going to process a files that sometimes is taking around 15 minutes. What to do now?
2. How to verify that the timeout limit was the latest change in the doc?

Agreed this is wrong and has changed recently.
The gcloud cli documentation suggests --gen2 is higher and 540s is the limit for --gen1:

I also had an environment was a --timeout=3600 which was working until quite recently. Something has changed :-/

The timeout has always been 540 seconds. See (and note the dates):

• https://stackoverflow.com/questions/62742049/google-cloud-function-max-timeout-540-seconds-not-working-for-client
• https://stackoverflow.com/questions/68732826/run-firebase-cloud-function-for-more-than-9-mins-540-sec

If you need more time for a background/async execution, you can either break up your function into different parts, or you can use a different product, such as Cloud Run. There is a full example of how to do that.

You could also arrange to use App Engine or Compute Engine to stand up a server.