Codex integration guide
Call semantics, pools, and failures
Choose links from execution intent and model failure flow explicitly.
When to use
Use explicit methods when execution differs from the service default or requires a pool, priority, parallelism, or error path.
Behavior
function_callinvokes the target directly under normal in-process semantics.task_pool_callsubmits work to a named pool;priority_task_pool_callalso requires an explicit priority.parallel_callexpresses concurrent fan-out rather than relying on declaration order.- An Error stream and error edge represent failure flow; they are not equivalent to a normal data edge.
Example
process_inventory.priority_task_pool_call(
reserve_inventory,
pool=inventory_workers,
priority=10,
)
process_inventory.error_to(inventory_error)