gcloud run jobs update --task-timeout => not working for >1 day

[nick-youngblut]

The task timeout for GCP Cloud Run times can be set up to 7 days in the GCP console.  However, since this option is in preview, trying to set the task timeout >1 day via the CLI:

```
gcloud run jobs update --task-timeout=7200m
```

...results in the following error:

```
ERROR: (gcloud.run.jobs.update) FAILED_PRECONDITION: The feature 'long-running-jobs' is not supported in the declared launch stage on resource sc-recounter-run. The launch stage annotation should be specified at least as BETA. Please visit https://cloud.google.com/run/docs/troubleshooting#launch-stage-validation for in-depth troubleshooting documentation.
```

https://cloud.google.com/run/docs/troubleshooting#launch-stage-validation does not provide helpful information for specifically running `gcloud run jobs`. 

The docs state: `"run.googleapis.com/launch-stage": "BETA"`
...but there appears to be no way of setting the launch stage via `gcloud run jobs update`.

How can one set the task timeout >1 day via `gcloud run jobs update`?  

[ronnelg]

Hi @nick-youngblut, 

Try to run it with gcloud beta run jobs update and see if it works:

gcloud beta run jobs update --task-timeout=7200m

Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.

[nick-youngblut · Accepted solution]

Yeah, that did it. 

I'm sure for dev-ops, `gcloud beta` is very useful, but it does lead to a confusing UX.