Hourglass.Activity.Info (hourglass v0.2.0)

Copy Markdown View Source

Per-dispatch context the runner threads through Hourglass.Activity.info/0.

An %Info{} is set in the activity-task process dictionary by Hourglass.ActivityRunner immediately before each dispatch and cleared (regardless of success or raise) immediately after. The values come straight off the inbound Coresdk.ActivityTask.Start proto and the surrounding ActivityTask envelope:

  • workflow_id — start.workflow_execution.workflow_id
  • run_id — start.workflow_execution.run_id (per-execution, stable across retries of the same attempt's activity)
  • activity_id — start.activity_id (server-assigned id, stable across retries of this scheduled activity)
  • attempt — start.attempt, normalised to a positive integer (an unset/zero uint32 clamps to 1; a dispatch is by definition an attempt)
  • task_token — the opaque binary token from the enclosing Coresdk.ActivityTask.ActivityTask.task_token; required to issue heartbeats via Hourglass.Activity.heartbeat/0
  • task_queue — the task-queue name the worker polled; required to route heartbeat calls through Hourglass.BridgeHolder

The (run_id, activity_id) pair is stable across retries of the same activity invocation, which is what the LLM call cache keys on to deduplicate retry double-spend.

Summary

Types

t()

Types

t()

@type t() :: %Hourglass.Activity.Info{
  activity_id: String.t(),
  attempt: pos_integer(),
  run_id: String.t(),
  task_queue: String.t() | nil,
  task_token: binary() | nil,
  workflow_id: String.t()
}