惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Last Week in AI
Last Week in AI
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
博客园_首页
雷峰网
雷峰网
IT之家
IT之家
I
InfoQ
酷 壳 – CoolShell
酷 壳 – CoolShell
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
B
Blog
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
博客园 - 【当耐特】
大猫的无限游戏
大猫的无限游戏
博客园 - 聂微东
Hugging Face - Blog
Hugging Face - Blog
A
About on SuperTechFans
月光博客
月光博客
P
Proofpoint News Feed
博客园 - 三生石上(FineUI控件)
J
Java Code Geeks
G
Google Developers Blog
小众软件
小众软件
宝玉的分享
宝玉的分享
Jina AI
Jina AI
V
Visual Studio Blog

Workflow SDK Documentation

Patterns for Defining Tools Human-in-the-Loop Building Durable AI Agents Queueing User Messages Resumable Streams Sleep, Suspense, and Scheduling Streaming Updates from Tools API Reference Workflow Globals Changelog Resilient run start Cookbook Building a World Deploying Astro Express Fastify Hono Getting Started NestJS Next.js Nitro Nuxt Python SvelteKit Vite corrupted-event-log fetch-in-workflow hook-conflict Errors
getWorldHandlers
2026-06-12 · via Workflow SDK Documentation

Build-time-safe access to the World's queue handlers without binding to runtime environment variables.

Returns a restricted view of the World exposing only the members that are safe to use at build time: createQueueHandler and specVersion. Framework adapters use it while generating workflow route handlers, before the deployment's runtime environment variables exist.

Unlike getWorld(), this function does not cache a fully configured World instance — caching at build time would lock in incomplete environment configuration.

import { getWorldHandlers } from "workflow/runtime";

const handlers = await getWorldHandlers(); 
console.log(handlers.specVersion);

Parameters

This function does not accept any parameters.

Returns

Returns a WorldHandlers object (synchronously in workflow 4.x; async in 5.x), where:

import type { World } from "@workflow/world";

type WorldHandlers = Pick<World, "createQueueHandler" | "specVersion">;

This is SDK infrastructure used by framework adapters and the workflow entrypoint. Application code should use getWorld() instead.