Pranay Prakash
516141647d
The entrypoint attached serializeTraceCarrier() (the CURRENT context) to step dispatches and requeues, where the node engine forwards the run-origin carrier via getNextTraceCarrier — in the default 'linked' trace mode this chained invocations to each other instead of linking each back to workflow.start in a star (observed empirically; contract pinned by runtime-trace-mode.test.ts). Thread the nextTraceCarrier closure from the runtime dispatch through runWorkflowWithQuickJS into every publish site, with serializeTraceCarrier as the standalone-call fallback. hook_conflict requeues also gain requestedAt for parity. (Unsigned; re-sign before pushing.) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Workflow SDK
Getting Started
The Workflow SDK lets you easily add durability, reliability, and observability to async JavaScript. Build apps and AI agents that can suspend, resume, and maintain state with ease.
Visit https://workflow-sdk.dev to view the full documentation.
Community
The Workflow SDK community can be found on GitHub Discussions, where you can ask questions, voice ideas, and share your projects with other people.
Contributing
Contributions to Workflow SDK are welcome and highly appreciated. Please use GitHub issues and discussions to collaborate with the team and wider community.
Security
If you believe you have found a security vulnerability in Workflow SDK, we encourage you to responsibly disclose this and not open a public issue.
To participate in our Open Source Software Bug Bounty program, please email responsible.disclosure@vercel.com. We will add you to the program and provide further instructions for submitting your report.