No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Did a bit of digging in my stack export and found the new ID is different than the ID:

`"id": "2022-06-06_23_03_18-5843176362055954902"`

```"outputs": {
  "id": "2022-06-07_08_21_12-44324234441230267",
   "jobId": "2022-06-07_08_21_12-44324234441230267",```

The resource docs you're referencing are from <https://github.com/pulumi/pulumi-gcp> instead of <https://github.com/pulumi/terraform-provider-google-beta>.

That being said, can you share the code where you're defining the flex template job? Dataflow is a bit odd in the sense that jobs can start and stop independently of a Pulumi run, so I suspect that there's some flag that we need to set to ensure Pulumi knows that it could change outside of the defined state. I don't know it that well, but I'm willing to try to help figure it out.

```const job = new gcp.dataflow.FlexTemplateJob(
      name,
      {
        name: name,
        containerSpecGcsPath: interpolate`<gs://stagingbucket/templates/spec>`,
        onDelete: 'drain',
        project: project,
        parameters: {
          setup_file: './src/python/setup.py',
          service_account_email: serviceAccount.email,
          ...
        },
      },
      resourceOptions,
    );```

Pretty simple definition, I manually create the flex template spec with

```const template: FlexTemplate = {
      defaultEnvironment: {},
      image: imageName,
      sdkInfo: {
        language: 'PYTHON',
      },
    };```