[ianmacartney]

Add completeTransactionally: true to enqueueMutation and enqueueMutationBatch. Successful work, its selected onComplete callback, and completion bookkeeping commit together. For example, if the callback writes a result and then throws, both its writes and the work's writes roll back instead of leaving successful work with a failed callback.

The existing mutation wrapper calls the completion helper directly, eliminating the separately scheduled completion mutation without adding another wrapper UDF. Completion errors escape the wrapper and fail the scheduled mutation; existing recovery later records a terminal failure and dispatches the failure callback if selected. The job occupies its concurrency slot until recovery runs. Ordinary work errors retain the existing failure-completion path. Default completion, failure/cancellation callbacks, and action/query execution retain their current behavior.

Based on current main, including merged #237 (status-filtered completion), with transactional mode restricted to mutations at the client type boundary and component runtime boundary. Batch items remain independent transactions. New stored and scheduled fields are optional for existing queued jobs. Nested work and success callback calls use transaction limits derived from remaining capacity, reserving room for bookkeeping. The existing Convex ^1.43 peer requirement covers nested transaction limits. The headroom helper reserves the database and scheduler resources used by completion bookkeeping, while allowing newer Convex versions to add unrelated transaction metrics.

Validation: build, typecheck, lint, formatting, and all 268 tests pass with Vitest 5.1 after restacking onto main. The local Convex deployment smoke check (npm run test:e2e) also passes, with generated component API files unchanged. Tests cover successful commits and payload cleanup, absent/filtered callbacks, rollback after callback errors and after late bookkeeping errors, actual scheduled-wrapper failure followed by recovery and deduplication, work errors, default callback behavior, stale wrapper replay, remaining-budget calculations, mutation batch routing, client rollback on callback failure for single and batch enqueue, cancellation, and action/query rejection before batch writes. Success-path tests also verify that no separate completion or callback mutation is scheduled.

Test limitations: convex-test 0.0.67 supports nested transactionLimits; component wrapper tests enable transaction-limit tracking. It does not simulate production OCC. It omits the error text from failed scheduled-job records, so recovery tests supply that missing field after an actual scheduled wrapper fails and rolls back.

Transactional query success is a separate stacked change in #239.

[pkg-pr-new]

Open in StackBlitz

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

commit: 2e19056

[cubic-dev-ai]

All reported issues were addressed across 15 files

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

Re-trigger cubic</sub>

[ianmacartney]

• Add transactional success completion for queries #239
• Add transactional success completion for mutations #238 👈 (View in Graphite)
• Filter onComplete callbacks by result status #237
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[cubic-dev-ai]

All reported issues were addressed across 4 files (changes from recent commits).

<sub>Tip: Review your code locally with the cubic CLI to iterate faster.

Re-trigger cubic</sub>