Skip to content

@workflow/nitro omits flow/step routes from Vercel BOA config.json on Nitro 3.x #2460

@aatosolavi

Description

@aatosolavi

Summary

On the Nitro 3.x vercel preset with workflow/nitro, the build emits:

  • functions/.well-known/workflow/v1/step.func
  • functions/.well-known/workflow/v1/flow.func
  • functions/.well-known/workflow/v1/webhook/[token].func
  • config.json route for /.well-known/workflow/v1/webhook/[token]
  • config.json routes for /.well-known/workflow/v1/flow and /.well-known/workflow/v1/step

Repro

  1. Nitro vercel preset + modules: ['workflow/nitro']
  2. nitro build → inspect .vercel/output/config.json

Same result on nitro-imessage-agent-template with NITRO_PRESET=vercel (workflow ^4.2.4, nitro latest beta).

Versions tried (agora-factory)

  • nitro@3.0.1-alpha.1 + workflow@4.4.0 / 4.5.0
  • nitro@3.0.260610-beta + vite@7 (separate build failure — kysely resolution)

Impact

Dispatch/orchestration appears to work via queue triggers + webhook route (approval hooks). Direct HTTP POST /.well-known/workflow/v1/step hits the app catch-all instead.

Request

Emit flow/step routes in config.json before filesystem/catch-all when functions are present, or document that queue-only invocation is the supported Vercel contract.


Reported from agora-factory Phase 0 experiment (2026-06-16).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions