Cloud Run Jobs take 90-120 seconds to start on us-central1, even with a minimal image.
I’ve so far used Cloud Run Services, also for jobs type tasks. They typically start in 2-3 seconds.
Now I tried switching over to Cloud Run Jobs and find it takes almost 2 minutes from creating the Job execution until the job actually starts running. Even for a hello world type job? Is this normal?
More detail: Cloud Run Jobs in us-central1 consistently take 90–120 seconds before the container actually begins producing stdout, even for a minimal prebuilt BusyBox image. The issue reproduces from both the Google Cloud Console and gcloud run jobs execute, so it is not related to Workflows. Provisioning appears quickly, but the execution does not actually start running until much later. We reproduced this with a minimal image to rule out Node, npm, application code, and source-based buildpacks.