Does enabling unauthenticated invocations on Cloud Run alter the 60‑minute request timeout limit?

Goal: Verify whether the 60‑minute request timeout enforced by Cloud Run applies equally to invocations that are allowed unauthenticated access, so that integration tests can rely on the same safety net without using production credentials.

Constraints: Cloud Run’s timeout is a hard upper bound that cannot be raised; it covers the entire request lifecycle, including container startup latency and response streaming. Enabling unauthenticated access is done by binding the run.invoker role to allUsers, which is documented but does not mention any timeout variation.

Uncertainty: The public documentation does not explicitly state whether the timeout measurement or error handling differs for unauthenticated requests, leaving it unclear if tests should expect identical 504 Gateway Timeout behavior.

• Is the 60‑minute timeout applied identically to unauthenticated invocations?
• Does the timeout count container startup latency the same way for unauthenticated calls?
• Does Cloud Run return the same HTTP 504 error when an unauthenticated request exceeds the limit?