google-cloud-transcoder job not starting immediately after user signup
htrappmaier opened this issue · 0 comments
htrappmaier commented
We're using google-cloud-transcoder services 3 years now - without any troubles -> working smoothly. The only issue we found: If a user starts a transcoder job (triggered via gcloud function) immediately after signup (with all necessary permissions granted) the job is not starting. After logout/login transcoder jobs are starting as expected. Is there a logical reason for this behaviour?
"firebase-functions": "^6.1.1",
"@google-cloud/pubsub": "^4.9.0",
"@google-cloud/storage": "^7.14.0",
"@google-cloud/video-transcoder": "^3.3.0",
goog-managed-by: cloudfunctions
goog-cloudfunctions-runtime: nodejs18
cloud.googleapis.com/location: europe-west1
run.googleapis.com/client-name: cli-firebase
cloudfunctions.googleapis.com/trigger-type: google.cloud.storage.object.v1.finalized