You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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?
The text was updated successfully, but these errors were encountered: