[ianmacartney]

When a queued function throws a ConvexError, Workpool currently keeps only its message. Workflow cannot reconstruct the original error or expose its structured data (convex/workflow#315).

Add optional errorData to failed RunResult values and their validators. Both mutation workers and action/query workers preserve the original Convex value while keeping existing message formatting, retry decisions, and NonRetryableError behavior. Ordinary errors and historical failures continue to work without the new field.

Validation: all 245 tests pass, including callback round-trips for queries, mutations, and retried actions; build, typecheck, lint, and format checks pass. An isolated native-backend test with the corresponding Workflow changes also passed all five execution modes plus nested workflows, including bigint and byte payloads through replay.

Related: convex/workflow#315. Companion Workflow PR: convex/workflow#316 reconstructs ConvexError from this payload.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/convex/workpool/@convex-dev/workpool@257

commit: ca813c0

[cubic-dev-ai]

All reported issues were addressed across 9 files

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[ianmacartney]

My only hesitation is whether errorData is a good name (vs. just data or convexErrorData or something)

[reeceyang]

cool, this seems like it could be also be useful for

• convex/workflow#310

to store the failed stepId in the RunResult instead of as part of an error message string