cloud run job has completed execution but platform still reports it as running

[breathe]

I have a cloud run job that seems to be stuck in the running state even though the last log statement output is "Container called exit(0)" which matches what I expect to see after the one process executed within the job completes and successfully exits.

It's quite bizarre to me that the job appears to still be running --

the ui shows the job as in 'running state' having completed 0 / 1 tasks and does not have an end time -- all of which suggest the cloud platform has not observed the job to have exited.

What's the deal here?  Is this a bug in the infra associated with reporting on a job that has exited?  Am I getting billed for this job even though its done and not actually running ...?

[bryan_shorebird]

Also seeing this—were you ever able to find a resolution? Am I just not being patient enough?

[lucasfml]

I'm also facing the same issue.

[alexandermoreno]

Hi, any info about this, I'm facing the same issue.

[knet]

Hi, this is unexpected. If any of you see this issue again, can you send me a private message with your project ID, so we can investigate?

Thanks,

Karolina

[knet]

Also: when you see this happen, is it only the UI that shows the job still running? Does it resolve if you reload the page? Or is this an issue across the UI and gcloud?