Skip to main content
These utilities expose runtime composition state for framework and wrapper authors. They aren’t business correlation keys. Prefer ordinary signal dependencies and correlationId when they express the relationship.

getNextHookLocation

Returns the next durable hook location without reserving it:
Call it immediately before the durable declaration a low-level wrapper associates with that location:
automations/report-hook-location.automation.ts
The function returns undefined outside an active automation traversal. Inspection doesn’t consume the slot. Hook locations identify replay structure, not business entities or occurrences.

getAutomationExecutionIdentity

Returns the active automation and context IDs during execution:
Planning has no execution context. Call the function from runtime code such as a custom action handler:
automations/report-execution-identity.automation.ts
Coordination operators create child contexts, so contextId can change as work progresses. Don’t use it as a correlation key; use correlationId or a provider ID.