iii-trigger-actions

name	iii-trigger-actions
description	Selects how functions are invoked: synchronous result-returning calls, fire-and-forget void dispatches, or durable `TriggerAction.Enqueue({ queue })` background jobs. Use whenever a handler should not block the caller, work should run later or reliably with retries, a request should return quickly, or an agent must choose between inline RPC, optional side effects, and queued async processing.

Trigger Actions

Comparable to: RPC vs message queue vs fire-and-forget patterns

Key Concepts

Use the concepts below when they fit the task. Not every invocation needs all three modes.

• Synchronous (default): caller blocks until the function returns a result or times out
• Void (TriggerAction.Void()): fire-and-forget dispatch, returns immediately, no retry guarantees
• Enqueue (TriggerAction.Enqueue({ queue })): routes through a named queue with automatic retries and backoff, returns a messageReceiptId
• Decision guide: need the result? use sync. Must complete reliably? use enqueue. Optional side effect? use void.

Architecture

The caller invokes trigger() with an optional action parameter. Synchronous mode waits for the handler result. Void mode dispatches and returns immediately. Enqueue mode places the payload on a named queue where a consumer processes it with retry guarantees.

iii Primitives Used

Primitive	Purpose
trigger({ function_id, payload })	Synchronous invocation, blocks for result
trigger({ ..., action: TriggerAction.Void() })	Fire-and-forget, returns immediately