Mastra•9mo ago•

5 replies

Workflow Type Inference Issue in Mastra 0.10.5

Summary

After updating from Mastra 0.10.3 to 0.10.5, we're experiencing TypeScript type inference issues with workflow chaining. The type system incorrectly expects all steps in a workflow chain to accept the parent workflow's input schema, rather than properly flowing types through the chain. At least, this is our current theory.

Environment

- Mastra Version: 0.10.5 (previously working on 0.10.3)
- TypeScript Version: 5.8.3
- Zod Version: 3.24.2
- Project: Monorepo using pnpm workspaces

Issue Description

When chaining workflows using

.then()

.then()

, TypeScript expects the chained workflow/step to accept the parent workflow's input schema instead of the output from the previous step in the chain.

Example Error

Type error: Argument of type 'Workflow<...>' is not assignable to parameter of type 'Step<...>'.
  Types of property 'inputSchema' are incompatible.
    Type '{ analysis: ZodObject<...>; links: ZodArray<...>; iteration: ZodNumber; }' is missing the following properties from type '{ concept: ZodObject<...>; throttleMaxKnownCompetitors: ...; linksAlreadyFound: ... }': concept, throttleMaxKnownCompetitors, linksAlreadyFound

Type error: Argument of type 'Workflow<...>' is not assignable to parameter of type 'Step<...>'.
  Types of property 'inputSchema' are incompatible.
    Type '{ analysis: ZodObject<...>; links: ZodArray<...>; iteration: ZodNumber; }' is missing the following properties from type '{ concept: ZodObject<...>; throttleMaxKnownCompetitors: ...; linksAlreadyFound: ... }': concept, throttleMaxKnownCompetitors, linksAlreadyFound

Code Example

Here's a simplified example that demonstrates the issue:

// Parent workflow expects: { concept, throttleMaxKnownCompetitors, linksAlreadyFound }
export const findKnownCompetitorsWorkflow = createWorkflow({
  id: "findKnownCompetitorsWorkflow",
  inputSchema: z.object({
    concept: conceptAnalysisSchema,
    throttleMaxKnownCompetitors: z.number(),
    linksAlreadyFound: z.array(linkSchema).default([]),
  }),
  outputSchema: z.object({
    competitions: z.array(competitionSchema),
  }),
  steps: [getAiLinks, crawlLinksWorkflow, classifyCompetitionsStep],
});

// Workflow chain with proper data mapping
findKnownCompetitorsWorkflow
  .then(getAiLinks)
  .map({
    // Correctly mapping to what crawlLinksWorkflow expects
    links: {
      step: getAiLinks,
      path: "links",
    },
    analysis: {
      initData: findKnownCompetitorsWorkflow,
      path: "concept.analysis",
    },
    iteration: {
      value: 0,
      schema: z.number(),
    },
  })
  .then(crawlLinksWorkflow) // ❌ Type error here!

// Parent workflow expects: { concept, throttleMaxKnownCompetitors, linksAlreadyFound }
export const findKnownCompetitorsWorkflow = createWorkflow({
  id: "findKnownCompetitorsWorkflow",
  inputSchema: z.object({
    concept: conceptAnalysisSchema,
    throttleMaxKnownCompetitors: z.number(),
    linksAlreadyFound: z.array(linkSchema).default([]),
  }),
  outputSchema: z.object({
    competitions: z.array(competitionSchema),
  }),
  steps: [getAiLinks, crawlLinksWorkflow, classifyCompetitionsStep],
});

// Workflow chain with proper data mapping
findKnownCompetitorsWorkflow
  .then(getAiLinks)
  .map({
    // Correctly mapping to what crawlLinksWorkflow expects
    links: {
      step: getAiLinks,
      path: "links",
    },
    analysis: {
      initData: findKnownCompetitorsWorkflow,
      path: "concept.analysis",
    },
    iteration: {
      value: 0,
      schema: z.number(),
    },
  })
  .then(crawlLinksWorkflow) // ❌ Type error here!

The

crawlLinksWorkflow

crawlLinksWorkflow

expects

{ analysis, links, iteration }

{ analysis, links, iteration }

which is exactly what we're providing via

.map()

.map()

, but TypeScript thinks it should receive the parent workflow's input

{ concept, throttleMaxKnownCompetitors, linksAlreadyFound }

{ concept, throttleMaxKnownCompetitors, linksAlreadyFound }

Impact

- Affects multiple workflows in our codebase
- Prevents TypeScript compilation without workarounds
- Removes type safety for workflow chains
- The issue appears after updating from 0.10.3 to 0.10.5

Expected Behavior

The type system should properly flow types through the workflow chain:
1. Parent workflow input → First step
2. First step output →

.map()

.map()

transformation → Second step
3. And so on...

Additional Context

- We noticed the zod package had two versions (3.24.4 and 3.25.56) in our monorepo, but aligning them didn't resolve the issue
- The same code worked correctly in Mastra 0.10.3
- The issue affects workflows used both in

steps

steps

arrays and in

.then()

.then()

chains

Any guidance would be greatly appreciated! Happy to provide more details or test potential fixes.

Mastra•9mo ago•

5 replies

flippyhead

Workflow Type Inference Issue in Mastra 0.10.5

Summary

Environment

- Mastra Version: 0.10.5 (previously working on 0.10.3)
- TypeScript Version: 5.8.3
- Zod Version: 3.24.2
- Project: Monorepo using pnpm workspaces

Issue Description

When chaining workflows using

.then()

.then()

, TypeScript expects the chained workflow/step to accept the parent workflow's input schema instead of the output from the previous step in the chain.

Example Error

Type error: Argument of type 'Workflow<...>' is not assignable to parameter of type 'Step<...>'.
  Types of property 'inputSchema' are incompatible.
    Type '{ analysis: ZodObject<...>; links: ZodArray<...>; iteration: ZodNumber; }' is missing the following properties from type '{ concept: ZodObject<...>; throttleMaxKnownCompetitors: ...; linksAlreadyFound: ... }': concept, throttleMaxKnownCompetitors, linksAlreadyFound

Type error: Argument of type 'Workflow<...>' is not assignable to parameter of type 'Step<...>'.
  Types of property 'inputSchema' are incompatible.
    Type '{ analysis: ZodObject<...>; links: ZodArray<...>; iteration: ZodNumber; }' is missing the following properties from type '{ concept: ZodObject<...>; throttleMaxKnownCompetitors: ...; linksAlreadyFound: ... }': concept, throttleMaxKnownCompetitors, linksAlreadyFound

Code Example

Here's a simplified example that demonstrates the issue:

// Parent workflow expects: { concept, throttleMaxKnownCompetitors, linksAlreadyFound }
export const findKnownCompetitorsWorkflow = createWorkflow({
  id: "findKnownCompetitorsWorkflow",
  inputSchema: z.object({
    concept: conceptAnalysisSchema,
    throttleMaxKnownCompetitors: z.number(),
    linksAlreadyFound: z.array(linkSchema).default([]),
  }),
  outputSchema: z.object({
    competitions: z.array(competitionSchema),
  }),
  steps: [getAiLinks, crawlLinksWorkflow, classifyCompetitionsStep],
});

// Workflow chain with proper data mapping
findKnownCompetitorsWorkflow
  .then(getAiLinks)
  .map({
    // Correctly mapping to what crawlLinksWorkflow expects
    links: {
      step: getAiLinks,
      path: "links",
    },
    analysis: {
      initData: findKnownCompetitorsWorkflow,
      path: "concept.analysis",
    },
    iteration: {
      value: 0,
      schema: z.number(),
    },
  })
  .then(crawlLinksWorkflow) // ❌ Type error here!

// Parent workflow expects: { concept, throttleMaxKnownCompetitors, linksAlreadyFound }
export const findKnownCompetitorsWorkflow = createWorkflow({
  id: "findKnownCompetitorsWorkflow",
  inputSchema: z.object({
    concept: conceptAnalysisSchema,
    throttleMaxKnownCompetitors: z.number(),
    linksAlreadyFound: z.array(linkSchema).default([]),
  }),
  outputSchema: z.object({
    competitions: z.array(competitionSchema),
  }),
  steps: [getAiLinks, crawlLinksWorkflow, classifyCompetitionsStep],
});

// Workflow chain with proper data mapping
findKnownCompetitorsWorkflow
  .then(getAiLinks)
  .map({
    // Correctly mapping to what crawlLinksWorkflow expects
    links: {
      step: getAiLinks,
      path: "links",
    },
    analysis: {
      initData: findKnownCompetitorsWorkflow,
      path: "concept.analysis",
    },
    iteration: {
      value: 0,
      schema: z.number(),
    },
  })
  .then(crawlLinksWorkflow) // ❌ Type error here!

The

crawlLinksWorkflow

crawlLinksWorkflow

expects

{ analysis, links, iteration }

{ analysis, links, iteration }

which is exactly what we're providing via

.map()

.map()

, but TypeScript thinks it should receive the parent workflow's input

{ concept, throttleMaxKnownCompetitors, linksAlreadyFound }

{ concept, throttleMaxKnownCompetitors, linksAlreadyFound }

Impact

- Affects multiple workflows in our codebase
- Prevents TypeScript compilation without workarounds
- Removes type safety for workflow chains
- The issue appears after updating from 0.10.3 to 0.10.5

Expected Behavior

The type system should properly flow types through the workflow chain:
1. Parent workflow input → First step
2. First step output →

.map()

.map()

transformation → Second step
3. And so on...

Additional Context

steps

steps

arrays and in

.then()

.then()

chains

Any guidance would be greatly appreciated! Happy to provide more details or test potential fixes.

Workflow Type Inference Issue in Mastra 0.10.5

Summary

Environment

Issue Description

Example Error

Code Example

Impact

Expected Behavior

Additional Context

Workflow Type Inference Issue in Mastra 0.10.5

Summary

Environment

Issue Description

Example Error

Code Example

Impact

Expected Behavior

Additional Context

Similar Threads

Similar Threads

Similar Threads