Playground incorrect rendering for workflow execution

There are 2 major issues with rendering workflow execution that I am facing.

All

.map()

.map()

step calls are rendered as

mapping_undefined

mapping_undefined

. If workflow has several mapping steps they render same execution state at the same time. Let's imagine I have workflow:

workflow
  .map(prepareParamsForTool)
  .then(someTool)
  .map(processToolOutput)

workflow
  .map(prepareParamsForTool)
  .then(someTool)
  .map(processToolOutput)

When this worklow is executed it renders as:

// 1
[mapping_undefined: Executing]
[someTool: not started]
[mapping_undefined: Executing]
// 2
[mapping_undefined: Success, Input, Output]
[someTool: Executing]
[mapping_undefined: Success, Input, Output]
// 3
[mapping_undefined: Executing]
[someTool: Success, Input, Output]
[mapping_undefined: Executing]
// 4
[mapping_undefined: Success, Input, Output]
[someTool: Success, Input, Output]
[mapping_undefined: Success, Input, Output]

// 1
[mapping_undefined: Executing]
[someTool: not started]
[mapping_undefined: Executing]
// 2
[mapping_undefined: Success, Input, Output]
[someTool: Executing]
[mapping_undefined: Success, Input, Output]
// 3
[mapping_undefined: Executing]
[someTool: Success, Input, Output]
[mapping_undefined: Executing]
// 4
[mapping_undefined: Success, Input, Output]
[someTool: Success, Input, Output]
[mapping_undefined: Success, Input, Output]

Both

mapping_undefined

mapping_undefined

are showing almost identical state: Input, Output, execution time. The only unique button that shows mapping function source code. I've tried to pass named functions instead of anonymous, but it still didn't pick up.

Second problem is somehow similar but on different level. All workflow execution rendered in agent thread also render same data for all instances of workflow execution rendered.

Mastra•6mo ago•

6 replies

Guria

Playground incorrect rendering for workflow execution

There are 2 major issues with rendering workflow execution that I am facing.

All

.map()

.map()

step calls are rendered as

mapping_undefined

mapping_undefined

. If workflow has several mapping steps they render same execution state at the same time. Let's imagine I have workflow:

workflow
  .map(prepareParamsForTool)
  .then(someTool)
  .map(processToolOutput)

workflow
  .map(prepareParamsForTool)
  .then(someTool)
  .map(processToolOutput)

When this worklow is executed it renders as:

// 1
[mapping_undefined: Executing]
[someTool: not started]
[mapping_undefined: Executing]
// 2
[mapping_undefined: Success, Input, Output]
[someTool: Executing]
[mapping_undefined: Success, Input, Output]
// 3
[mapping_undefined: Executing]
[someTool: Success, Input, Output]
[mapping_undefined: Executing]
// 4
[mapping_undefined: Success, Input, Output]
[someTool: Success, Input, Output]
[mapping_undefined: Success, Input, Output]

// 1
[mapping_undefined: Executing]
[someTool: not started]
[mapping_undefined: Executing]
// 2
[mapping_undefined: Success, Input, Output]
[someTool: Executing]
[mapping_undefined: Success, Input, Output]
// 3
[mapping_undefined: Executing]
[someTool: Success, Input, Output]
[mapping_undefined: Executing]
// 4
[mapping_undefined: Success, Input, Output]
[someTool: Success, Input, Output]
[mapping_undefined: Success, Input, Output]

Both

mapping_undefined

mapping_undefined

Playground incorrect rendering for workflow execution

Similar Threads

Playground incorrect rendering for workflow execution

Similar Threads

Similar Threads

Similar Threads