Closing Threads - Threadify Documentation

Contract threads close automatically at a terminal step. Close non-contract threads explicitly as completed or cancelled. Once closed, a thread cannot resume or accept additional steps. Its key remains bound to that thread; use a new key for a new execution.

Manual completion is rejected for contract-based threads unless a terminal step has been reached.

Basic Usage

const thread = await threadify.thread('order:ORD-123', { label: 'Order ORD-123' }); // No contract

// Record some steps
await thread.step('process_order').success();
await thread.step('send_email').success();

// Manually end the thread
await thread.complete('All steps finished');
// OR
await thread.cancel('User cancelled order');

thread, _ := conn.Thread(ctx, "order:ORD-123", threadify.ThreadOptions{Label: "Order ORD-123"}) // No contract

// Record some steps
thread.Step("process_order").Success(ctx)
thread.Step("send_email").Success(ctx)

// Manually end the thread
thread.Complete(ctx, "All steps finished")
// OR
thread.Cancel(ctx, "User cancelled order")

thread = await connection.thread("order:ORD-123", {"label": "Order ORD-123"})  # No contract

# Record some steps
await thread.step("process_order").success()
await thread.step("send_email").success()

# Manually end the thread
await thread.complete("All steps finished")
# OR
await thread.close("User cancelled order")

Methods

SDK	Complete	Cancel
JavaScript	`complete(reason?)`	`cancel(reason?)`
Go	`Complete(ctx, reason?)`	`Cancel(ctx, reason?)`
Python	`complete(reason?)`	`close(reason?)`

Notifications

When a thread ends, Threadify emits events:

thread.completed - Triggered when complete() is called or a terminal step is reached
thread.cancelled - Triggered when cancel() is called