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

推荐订阅源

H
Help Net Security
腾讯CDC
爱范儿
爱范儿
Google DeepMind News
Google DeepMind News
V
V2EX
Blog — PlanetScale
Blog — PlanetScale
Engineering at Meta
Engineering at Meta
GbyAI
GbyAI
量子位
F
Fortinet All Blogs
G
Google Developers Blog
T
The Blog of Author Tim Ferriss
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Hugging Face - Blog
Hugging Face - Blog
Last Week in AI
Last Week in AI
T
Tailwind CSS Blog
J
Java Code Geeks
S
SegmentFault 最新的问题
D
Docker
博客园 - 司徒正美
The GitHub Blog
The GitHub Blog
Jina AI
Jina AI
M
MIT News - Artificial intelligence
博客园 - 【当耐特】

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
observabilityRevivers
2026-06-12 · via Workflow SDK Documentation

Standard reviver functions for deserializing workflow data types in observability tools.

A set of reviver functions that handle the workflow serialization format's workflow-specific types — streams, step/workflow function references, class instances, AbortController/AbortSignal, and DOMException — reviving them as display-friendly marker objects or strings. Built-in JavaScript types (Date, Map, Set, RegExp, etc.) are handled by the devalue format itself and need no revivers.

Pass it as the revivers argument to hydrateResourceIO() or hydrateData().

import { hydrateResourceIO, observabilityRevivers } from "workflow/observability"; 
import type { Step } from "@workflow/world";
declare const step: Step; // @setup

const hydrated = hydrateResourceIO(step, observabilityRevivers); 
import type { Revivers } from "workflow/observability";

declare const observabilityRevivers: Revivers;

Where Revivers is:

type Revivers = Record<string, (value: any) => any>;

Each key is a serialized type tag, and each function revives a serialized value of that type. You can spread observabilityRevivers into a custom reviver map to override how specific types are displayed:

import { hydrateData, observabilityRevivers } from "workflow/observability";
declare const value: unknown; // @setup

const customRevivers = {
  ...observabilityRevivers,
  // Render stream references as plain strings instead of marker objects
  ReadableStream: () => "<stream>",
};

const hydrated = hydrateData(value, customRevivers);