Skip to content

Fix step functions nested multiple levels deep in an object#923

Merged
TooTallNate merged 4 commits intomainfrom
02-03-fix_step_functions_nested_multiple_levels_deep_in_an_object
Feb 7, 2026
Merged

Fix step functions nested multiple levels deep in an object#923
TooTallNate merged 4 commits intomainfrom
02-03-fix_step_functions_nested_multiple_levels_deep_in_an_object

Conversation

@TooTallNate
Copy link
Member

@TooTallNate TooTallNate commented Feb 3, 2026

Fixed a bug where step functions nested multiple levels deep in an object weren't being properly transformed.

What changed?

  • Enhanced the SWC plugin to recursively process nested objects to find step functions
  • Added support for step functions defined inside deeply nested object properties, including function call arguments
  • Implemented proper path handling for nested step IDs, using compound paths (e.g., vade/tools/VercelRequest/execute)
  • Fixed variable name generation by replacing slashes with $ to create valid JavaScript identifiers
  • Updated documentation with examples of nested object property step functions
  • Added test cases for deeply nested step functions and agent tool steps

How to test?

Test with code that has step functions nested multiple levels deep in objects:

export const config = createConfig({
  level1: {
    level2: {
      level3: {
        myStep: async (input) => {
          "use step";
          return input * 2;
        },
      },
    },
  },
});

Or with agent tools:

export const vade = agent({
  tools: {
    VercelRequest: {
      execute: async (input, ctx) => {
        "use step";
        return 1 + 1;
      },
    },
  },
});

Why make this change?

This fix ensures that step functions can be properly identified and transformed regardless of how deeply they are nested in object structures. This is particularly important for complex configurations like agent tools where step functions might be several levels deep in the object hierarchy.

@changeset-bot
Copy link

changeset-bot bot commented Feb 3, 2026

🦋 Changeset detected

Latest commit: 8cee6a5

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 15 packages
Name Type
@workflow/swc-plugin Patch
@workflow/astro Patch
@workflow/builders Patch
@workflow/cli Patch
@workflow/nest Patch
@workflow/next Patch
@workflow/nitro Patch
@workflow/rollup Patch
@workflow/sveltekit Patch
workflow Patch
@workflow/vite Patch
@workflow/world-testing Patch
@workflow/nuxt Patch
@workflow/core Patch
@workflow/web-shared Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@github-actions
Copy link
Contributor

github-actions bot commented Feb 3, 2026

📊 Benchmark Results

📈 Comparing against baseline from main branch. Green 🟢 = faster, Red 🔺 = slower.

workflow with no steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Nitro 0.032s (-2.7%) 1.006s (~) 0.974s 10 1.00x
💻 Local Express 0.033s (+2.8%) 1.007s (~) 0.975s 10 1.02x
💻 Local Next.js (Turbopack) 0.047s 1.008s 0.961s 10 1.47x
🐘 Postgres Nitro 0.104s (-77.0% 🟢) 1.011s (~) 0.907s 10 3.23x
🐘 Postgres Express 0.190s (+6.5% 🔺) 1.012s (~) 0.822s 10 5.90x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 0.720s (-14.3% 🟢) 2.100s (-1.8%) 1.380s 10 1.00x
▲ Vercel Next.js (Turbopack) 0.872s (+5.5% 🔺) 2.245s (+2.7%) 1.373s 10 1.21x
▲ Vercel Nitro 0.924s (-23.1% 🟢) 2.246s (-17.3% 🟢) 1.322s 10 1.28x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

workflow with 1 step

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 1.105s 2.006s 0.901s 10 1.00x
💻 Local Nitro 1.105s (~) 2.005s (~) 0.901s 10 1.00x
💻 Local Express 1.106s (~) 2.005s (~) 0.899s 10 1.00x
🐘 Postgres Express 2.195s (-4.4%) 3.013s (~) 0.818s 10 1.99x
🐘 Postgres Nitro 2.477s (+4.4%) 3.014s (~) 0.536s 10 2.24x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.688s (-1.7%) 3.788s (+1.7%) 1.100s 10 1.00x
▲ Vercel Next.js (Turbopack) 2.695s (-1.8%) 3.701s (+3.1%) 1.006s 10 1.00x
▲ Vercel Express 2.712s (-0.8%) 3.651s (-8.6% 🟢) 0.939s 10 1.01x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

workflow with 10 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 10.744s 11.021s 0.276s 3 1.00x
💻 Local Nitro 10.818s (~) 11.020s (~) 0.202s 3 1.01x
💻 Local Express 10.830s (~) 11.022s (~) 0.192s 3 1.01x
🐘 Postgres Nitro 20.329s (~) 21.059s (~) 0.729s 2 1.89x
🐘 Postgres Express 20.413s (~) 21.055s (~) 0.642s 2 1.90x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 19.535s (-2.0%) 20.698s (-0.8%) 1.163s 2 1.00x
▲ Vercel Nitro 20.051s (+1.1%) 20.989s (-2.8%) 0.938s 2 1.03x
▲ Vercel Next.js (Turbopack) 20.418s (+0.8%) 21.251s (-2.0%) 0.833s 2 1.05x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

workflow with 25 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 27.274s 28.039s 0.766s 3 1.00x
💻 Local Nitro 27.457s (~) 28.043s (~) 0.586s 3 1.01x
💻 Local Express 27.478s (~) 28.040s (~) 0.563s 3 1.01x
🐘 Postgres Express 38.264s (-23.8% 🟢) 38.589s (-24.5% 🟢) 0.325s 2 1.40x
🐘 Postgres Nitro 50.351s (~) 51.122s (~) 0.771s 2 1.85x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 48.803s (-1.9%) 50.129s (-1.3%) 1.327s 2 1.00x
▲ Vercel Nitro 49.538s (+0.5%) 51.129s (+1.6%) 1.591s 2 1.02x
▲ Vercel Next.js (Turbopack) 49.987s (-2.2%) 50.996s (-2.1%) 1.009s 2 1.02x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

workflow with 50 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 56.733s 57.102s 0.369s 2 1.00x
💻 Local Express 57.158s (~) 58.101s (~) 0.943s 2 1.01x
💻 Local Nitro 57.184s (~) 58.098s (+1.8%) 0.913s 2 1.01x
🐘 Postgres Nitro 75.221s (-25.0% 🟢) 75.662s (-25.3% 🟢) 0.441s 2 1.33x
🐘 Postgres Express 76.508s (-23.8% 🟢) 77.174s (-23.8% 🟢) 0.665s 2 1.35x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 104.207s (-1.1%) 105.570s (-1.1%) 1.363s 1 1.00x
▲ Vercel Express 105.439s (+0.8%) 106.653s (~) 1.214s 1 1.01x
▲ Vercel Next.js (Turbopack) 108.473s (-1.0%) 109.290s (-1.7%) 0.817s 1 1.04x

🔍 Observability: Nitro | Express | Next.js (Turbopack)

Promise.all with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Nitro 1.402s (~) 2.005s (~) 0.603s 15 1.00x
💻 Local Next.js (Turbopack) 1.419s 2.005s 0.586s 15 1.01x
💻 Local Express 1.420s (~) 2.005s (~) 0.585s 15 1.01x
🐘 Postgres Nitro 2.016s (-16.2% 🟢) 2.597s (-13.8% 🟢) 0.581s 12 1.44x
🐘 Postgres Express 2.174s (-10.9% 🟢) 2.830s (-6.1% 🟢) 0.656s 11 1.55x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 3.060s (+18.2% 🔺) 4.116s (+17.4% 🔺) 1.056s 8 1.00x
▲ Vercel Express 3.177s (+11.1% 🔺) 4.376s (+16.7% 🔺) 1.200s 7 1.04x
▲ Vercel Next.js (Turbopack) 3.420s (+13.9% 🔺) 4.504s (+12.8% 🔺) 1.084s 7 1.12x

🔍 Observability: Nitro | Express | Next.js (Turbopack)

Promise.all with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Express 2.512s (-4.9%) 3.007s (~) 0.495s 10 1.00x
💻 Local Nitro 2.577s (+0.8%) 3.007s (~) 0.430s 10 1.03x
💻 Local Next.js (Turbopack) 2.607s 3.007s 0.400s 10 1.04x
🐘 Postgres Nitro 9.381s (+9.1% 🔺) 10.044s (+11.3% 🔺) 0.663s 3 3.73x
🐘 Postgres Express 9.787s (+24.2% 🔺) 10.364s (+25.2% 🔺) 0.577s 3 3.90x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 3.157s (~) 4.259s (-2.0%) 1.102s 8 1.00x
▲ Vercel Nitro 3.461s (+6.1% 🔺) 4.544s (+4.2%) 1.084s 7 1.10x
▲ Vercel Next.js (Turbopack) 3.836s (+21.2% 🔺) 5.322s (+29.0% 🔺) 1.486s 6 1.22x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

Promise.all with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Express 7.270s (-4.6%) 8.027s (~) 0.757s 4 1.00x
💻 Local Nitro 7.447s (+3.9%) 8.019s (~) 0.572s 4 1.02x
💻 Local Next.js (Turbopack) 7.728s 8.267s 0.540s 4 1.06x
🐘 Postgres Express 50.987s (+4.0%) 51.106s (+4.0%) 0.119s 1 7.01x
🐘 Postgres Nitro 51.006s (+3.7%) 51.113s (+2.0%) 0.107s 1 7.02x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 5.405s (+64.4% 🔺) 6.849s (+47.2% 🔺) 1.444s 5 1.00x
▲ Vercel Next.js (Turbopack) 7.246s (+91.6% 🔺) 8.526s (+68.3% 🔺) 1.280s 4 1.34x
▲ Vercel Nitro 7.717s (+105.8% 🔺) 9.157s (+73.5% 🔺) 1.440s 4 1.43x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

Promise.race with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 1.419s 2.004s 0.586s 15 1.00x
💻 Local Nitro 1.420s (~) 2.005s (~) 0.585s 15 1.00x
💻 Local Express 1.422s (~) 2.005s (~) 0.582s 15 1.00x
🐘 Postgres Nitro 2.102s (+2.9%) 2.513s (-8.3% 🟢) 0.410s 12 1.48x
🐘 Postgres Express 2.117s (+12.1% 🔺) 2.740s (+5.6% 🔺) 0.623s 11 1.49x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 2.754s (-4.4%) 3.694s (-6.8% 🟢) 0.940s 9 1.00x
▲ Vercel Express 2.882s (+5.7% 🔺) 3.859s (+6.8% 🔺) 0.977s 9 1.05x
▲ Vercel Nitro 3.001s (+13.7% 🔺) 4.203s (+14.4% 🔺) 1.202s 8 1.09x

🔍 Observability: Next.js (Turbopack) | Express | Nitro

Promise.race with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 2.625s 3.007s 0.382s 10 1.00x
💻 Local Nitro 2.660s (~) 3.007s (~) 0.347s 10 1.01x
💻 Local Express 2.676s (-1.0%) 3.007s (~) 0.331s 10 1.02x
🐘 Postgres Nitro 12.026s (+2.3%) 12.705s (+5.6% 🔺) 0.680s 3 4.58x
🐘 Postgres Express 12.034s (+15.0% 🔺) 12.697s (+15.1% 🔺) 0.663s 3 4.58x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.854s (-11.2% 🟢) 3.994s (-22.6% 🟢) 1.140s 8 1.00x
▲ Vercel Next.js (Turbopack) 3.073s (-5.4% 🟢) 4.361s (+0.8%) 1.288s 7 1.08x
▲ Vercel Nitro 3.077s (~) 4.475s (-14.4% 🟢) 1.399s 7 1.08x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

Promise.race with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Nitro 7.662s (-4.5%) 8.020s (-5.9% 🟢) 0.358s 4 1.00x
💻 Local Express 7.846s (~) 8.269s (+3.0%) 0.423s 4 1.02x
💻 Local Next.js (Turbopack) 8.075s 8.517s 0.442s 4 1.05x
🐘 Postgres Express 51.742s (~) 52.140s (~) 0.398s 1 6.75x
🐘 Postgres Nitro 54.465s (~) 55.111s (~) 0.646s 1 7.11x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 3.344s (-2.8%) 4.576s (-2.8%) 1.233s 7 1.00x
▲ Vercel Nitro 3.719s (+4.5%) 5.147s (~) 1.428s 7 1.11x
▲ Vercel Next.js (Turbopack) 3.739s (~) 5.245s (+1.2%) 1.507s 6 1.12x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

Stream Benchmarks (includes TTFB metrics)
workflow with stream

💻 Local Development

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 0.144s 1.001s 0.010s 1.015s 0.871s 10 1.00x
💻 Local Nitro 0.170s (-0.9%) 1.002s (~) 0.010s (-2.9%) 1.015s (~) 0.846s 10 1.17x
💻 Local Express 0.172s (+1.2%) 1.002s (~) 0.010s (-1.0%) 1.015s (~) 0.843s 10 1.19x
🐘 Postgres Express 1.169s (-51.3% 🟢) 1.938s (-26.6% 🟢) 0.001s (+16.7% 🔺) 2.013s (-33.2% 🟢) 0.844s 10 8.10x
🐘 Postgres Nitro 1.272s (-48.1% 🟢) 1.768s (-31.7% 🟢) 0.001s (~) 2.013s (-33.2% 🟢) 0.741s 10 8.81x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - - -

▲ Production (Vercel)

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.446s (-4.5%) 2.871s (-3.9%) 0.172s (-30.1% 🟢) 3.732s (-5.5% 🟢) 1.285s 10 1.00x
▲ Vercel Express 2.625s (+2.2%) 3.197s (+14.0% 🔺) 0.181s (-19.8% 🟢) 3.998s (+7.1% 🔺) 1.374s 10 1.07x
▲ Vercel Next.js (Turbopack) 2.700s (~) 3.167s (+5.2% 🔺) 0.295s (+7.2% 🔺) 4.153s (+5.1% 🔺) 1.453s 10 1.10x

🔍 Observability: Nitro | Express | Next.js (Turbopack)

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World 🥇 Fastest Framework Wins
💻 Local Next.js (Turbopack) 7/12
🐘 Postgres Nitro 7/12
▲ Vercel Express 7/12
Fastest World by Framework

Winner determined by most benchmark wins

Framework 🥇 Fastest World Wins
Express 💻 Local 10/12
Next.js (Turbopack) 💻 Local 10/12
Nitro 💻 Local 11/12
Column Definitions
  • Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
  • TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
  • Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
  • Wall Time: Total testbench time (trigger workflow + poll for result)
  • Overhead: Testbench overhead (Wall Time - Workflow Time)
  • Samples: Number of benchmark iterations run
  • vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

  • 💻 Local: In-memory filesystem world (local development)
  • 🐘 Postgres: PostgreSQL database world (local development)
  • ▲ Vercel: Vercel production/preview deployment
  • 🌐 Starter: Community world (local development)
  • 🌐 Turso: Community world (local development)
  • 🌐 MongoDB: Community world (local development)
  • 🌐 Redis: Community world (local development)
  • 🌐 Jazz: Community world (local development)

📋 View full workflow run

@github-actions
Copy link
Contributor

github-actions bot commented Feb 3, 2026

🧪 E2E Test Results

Some tests failed

Summary

Passed Failed Skipped Total
✅ ▲ Vercel Production 479 0 38 517
✅ 💻 Local Development 408 0 62 470
✅ 📦 Local Production 408 0 62 470
✅ 🐘 Local Postgres 408 0 62 470
✅ 🪟 Windows 44 0 3 47
❌ 🌍 Community Worlds 31 157 12 200
✅ 📋 Other 120 0 21 141
Total 1898 157 260 2315

❌ Failed Tests

🌍 Community Worlds (157 failed)

mongodb (39 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

redis (39 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

starter (40 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • health check (CLI) - workflow health command reports healthy endpoints
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

turso (39 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

Details by Category

✅ ▲ Vercel Production
App Passed Failed Skipped
✅ astro 43 0 4
✅ example 43 0 4
✅ express 43 0 4
✅ fastify 43 0 4
✅ hono 43 0 4
✅ nextjs-turbopack 46 0 1
✅ nextjs-webpack 46 0 1
✅ nitro 43 0 4
✅ nuxt 43 0 4
✅ sveltekit 43 0 4
✅ vite 43 0 4
✅ 💻 Local Development
App Passed Failed Skipped
✅ astro-stable 40 0 7
✅ express-stable 40 0 7
✅ fastify-stable 40 0 7
✅ hono-stable 40 0 7
✅ nextjs-turbopack-stable 44 0 3
✅ nextjs-webpack-stable 44 0 3
✅ nitro-stable 40 0 7
✅ nuxt-stable 40 0 7
✅ sveltekit-stable 40 0 7
✅ vite-stable 40 0 7
✅ 📦 Local Production
App Passed Failed Skipped
✅ astro-stable 40 0 7
✅ express-stable 40 0 7
✅ fastify-stable 40 0 7
✅ hono-stable 40 0 7
✅ nextjs-turbopack-stable 44 0 3
✅ nextjs-webpack-stable 44 0 3
✅ nitro-stable 40 0 7
✅ nuxt-stable 40 0 7
✅ sveltekit-stable 40 0 7
✅ vite-stable 40 0 7
✅ 🐘 Local Postgres
App Passed Failed Skipped
✅ astro-stable 40 0 7
✅ express-stable 40 0 7
✅ fastify-stable 40 0 7
✅ hono-stable 40 0 7
✅ nextjs-turbopack-stable 44 0 3
✅ nextjs-webpack-stable 44 0 3
✅ nitro-stable 40 0 7
✅ nuxt-stable 40 0 7
✅ sveltekit-stable 40 0 7
✅ vite-stable 40 0 7
✅ 🪟 Windows
App Passed Failed Skipped
✅ nextjs-turbopack 44 0 3
❌ 🌍 Community Worlds
App Passed Failed Skipped
✅ mongodb-dev 3 0 0
❌ mongodb 5 39 3
✅ redis-dev 3 0 0
❌ redis 5 39 3
✅ starter-dev 3 0 0
❌ starter 4 40 3
✅ turso-dev 3 0 0
❌ turso 5 39 3
✅ 📋 Other
App Passed Failed Skipped
✅ e2e-local-dev-nest-stable 40 0 7
✅ e2e-local-postgres-nest-stable 40 0 7
✅ e2e-local-prod-nest-stable 40 0 7

📋 View full workflow run

@vercel
Copy link
Contributor

vercel bot commented Feb 3, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
example-nextjs-workflow-turbopack Error Error Feb 7, 2026 8:51am
example-nextjs-workflow-webpack Error Error Feb 7, 2026 8:51am
example-workflow Error Error Feb 7, 2026 8:51am
workbench-astro-workflow Error Error Feb 7, 2026 8:51am
workbench-express-workflow Error Error Feb 7, 2026 8:51am
workbench-fastify-workflow Error Error Feb 7, 2026 8:51am
workbench-hono-workflow Error Error Feb 7, 2026 8:51am
workbench-nitro-workflow Error Error Feb 7, 2026 8:51am
workbench-nuxt-workflow Error Error Feb 7, 2026 8:51am
workbench-sveltekit-workflow Error Error Feb 7, 2026 8:51am
workbench-vite-workflow Error Error Feb 7, 2026 8:51am
workflow-docs Error Error Feb 7, 2026 8:51am
workflow-nest Error Error Feb 7, 2026 8:51am
workflow-swc-playground Error Error Feb 7, 2026 8:51am

Copy link
Member Author

TooTallNate commented Feb 3, 2026

- Add test fixture for shorthand method syntax (async execute() { ... }) in nested object properties
- Fix bug where slash characters weren't being replaced with $ in variable references for shorthand methods
- Update spec.md to document shorthand method syntax support

This addresses the PR review comment asking about non-arrow functions in nested object step properties.
@TooTallNate TooTallNate force-pushed the 02-03-fix_step_functions_nested_multiple_levels_deep_in_an_object branch from 5b84bf9 to 8cee6a5 Compare February 7, 2026 08:17
@TooTallNate TooTallNate requested review from a team and pranaygp February 7, 2026 09:39
@TooTallNate TooTallNate merged commit ef23b0b into main Feb 7, 2026
140 of 155 checks passed
@TooTallNate TooTallNate deleted the 02-03-fix_step_functions_nested_multiple_levels_deep_in_an_object branch February 7, 2026 19:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants