Skip to content

bug: run.taskIdentifier shows unknown when calling batch.triggerAndWait and batch.triggerByTaskAndWait #2942

@napon

Description

@napon

Provide environment information

System:
OS: macOS 15.7.2
CPU: (14) arm64 Apple M3 Max
Memory: 2.72 GB / 36.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 22.21.1 - /Users/napon/.asdf/installs/nodejs/lts/bin/node
npm: 10.9.4 - /Users/napon/.asdf/plugins/nodejs/shims/npm
pnpm: 8.12.0 - /opt/homebrew/bin/pnpm
Watchman: 2025.11.10.00 - /opt/homebrew/bin/watchman

Describe the bug

code snippet:

const { runs } = await batch.triggerByTaskAndWait([
      { task: generateAudio, payload: {
        // ...
      } },
      ...scenes.map(scene => 
        ({ 
          task: generateScene, 
          payload: { 
            //...
          }
        })
      ),
    ]);


    logger.info(runs[0].taskIdentifier); // => unknown but it should be either 'generate-audio' or 'generate-scene'

Reproduction repo

N/A

To reproduce

code snippet:

const { runs } = await batch.triggerByTaskAndWait([
      { task: generateAudio, payload: {
        // ...
      } },
      ...scenes.map(scene => 
        ({ 
          task: generateScene, 
          payload: { 
            //...
          }
        })
      ),
    ]);


    logger.info(runs[0].taskIdentifier); // => unknown but it should be either 'generate-audio' or 'generate-scene'

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions