IssueTracker

We're using google-cloud-transcoder services for 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 resp. login at an other device, jobs are starting as expected. Is there a logical reason for this behaviour?

The job is triggered in gc functions onObjectFinalized when/after uploading a mp4/mov video file:
  exports.transcodeVideoFile = onObjectFinalized({cpu: 2, region: 'europe-west1'}, async (event) => {...}


  const {TranscoderServiceClient} = require('@google-cloud/video-transcoder').v1;
  const transcoderServiceClient = new TranscoderServiceClient();
 
  const jobconfig = createJobConfig( subfoldername, inputUri, outputUri, projectId, topic);
  const jobname = await createJobFromConfig(projectId, location, inputUri, outputUri, jobconfig, preset);

  async function createJobFromConfig(projectId, location, inputUri, outputUri, jobconfig, preset) {
    const request = {
       parent: transcoderServiceClient.locationPath(projectId, location),
       job: {
        inputUri: inputUri,
        outputUri: outputUri,
        config: jobconfig
       }
    };
    // Run request
     const [response] = await transcoderServiceClient.createJob(request);
     return response.name;
  }