Temporal Cloud Actions

Temporal Cloud Actions are the primary unit of consumption-based pricing for Temporal Cloud. They track billable operations within the Temporal Cloud Service, such as starting Workflows, recording a Heartbeat, or sending Signals.

Actions can be largely placed in the following categories:

• Workflow
• Activity
• Timer
• Signal
• Query
• Update
• Schedule
• Nexus

Some additional Temporal Cloud features are billed as Actions:

• Export
• Fairness
• Capacity

Actions that occur during Workflow Replay do not count towards billed Actions. Replay happens only on the Worker side to reconstruct Workflow state from Event History and does not generate new server-side operations.

Billable Actions are visible in the OpenMetrics endpoint, Workflow History and Usage Dashboards, and the Billing API. Action types and categories can help estimate usage, identify specific Action types that are driving usage, optimize workflows by tracking usage spikes, and troubleshoot errors. For example:

• You can see if a new Workflow type on a Namespace is driving a significant usage increase
• You can identify the aggregate usage of Activity Heartbeats on a Namespace

The following is the mapping of Action Categories to Action types. The Action Types that are visible on various endpoints can differ based on what is visible to a system. Action Categories and Action Types are not available in the billing API.

Usage and Billing data will have the most complete Actions data while Workflow history and metrics will help with detailed estimates. For example, History Event Types are provided for transparency, but do not always have a simple 1:1 relationship with Action Types. The Categories, Action types, and available endpoints are listed in the following sections:

Workflow

• Workflow started
  • Occurs via client start, Continue-As-New, Child Workflow start.
  • If a Workflow start fails, an Action is not recorded.
  • De-duplicated Workflow starts that share a Workflow ID do not count as an Action.
• Workflow reset
  • Occurs when a Workflow is reset.
  • Actions that occur before a Reset are counted on the original workflow. These events are not counted on the newly created workflow.
• Search Attribute upsert requested
  • Occurs for each invocation of UpsertSearchAttributes command.
  • Multiple Search Attributes updated in a single UpsertSearchAttributes command count as one Action.
  • Search Attributes specified during Workflow start are excluded from Action counts.
  • The TemporalChangeVersion Search Attribute, used for Workflow versioning, is also exempt from Action counting.
• Workflow Execution Options updated.
  • Occurs for every Workflow-Execution-Options-Updated event.
  • This includes attaching a Workflow completion callback or modifying a Workflow versioning override.
• Start Child Workflow Execution initiated.
  • Occurs when the parent Workflow durably records the intent to start a Child Workflow.
  • Results in two Actions, one for durably storing the intent to start a Child Workflow and one for the attempt to start it.
• Workflow started via Multi-Operation.
  • Occurs when a Workflow is started as part of an ExecuteMultiOperation request — a single atomic RPC that bundles a Workflow start with one or more Workflow Updates. The start counts as one Action.
  • Each bundled Update that is accepted or rejected counts as an additional Action.
  • If the Workflow was already running and the start is de-duplicated, no Action is charged for the start (though an update_workflow_options_via_start Action may still apply).

Usage Name	Metric Name	History Event Type
Start Workflow	start_workflow	EVENT_TYPE_WORKFLOW_EXECUTION_STARTED
Start Child Workflow	start_child_workflow	EVENT_TYPE_START_CHILD_WORKFLOW_EXECUTION_INITIATED
Continue As New Workflow	continue_as_new_workflow	EVENT_TYPE_WORKFLOW_EXECUTION_CONTINUED_AS_NEW Note: The UI shows a billable action only for the EVENT_TYPE_WORKFLOW_EXECUTION_STARTED event of the newly started Workflow, not for this history event.
Start Workflow (Multi-Operation)	start_workflow_multi_operation	EVENT_TYPE_WORKFLOW_EXECUTION_STARTED
Update Workflow Options	update_workflow_options	EVENT_TYPE_WORKFLOW_EXECUTION_OPTIONS_UPDATED
Update Workflow Options (Via Start)	update_workflow_options_via_start	EVENT_TYPE_WORKFLOW_EXECUTION_OPTIONS_UPDATED
Upsert Workflow Search Attributes	upsert_workflow_search_attributes	EVENT_TYPE_UPSERT_WORKFLOW_SEARCH_ATTRIBUTES
Reset Workflow	reset_workflow	EVENT_TYPE_WORKFLOW_TASK_FAILED Note: When cause == WORKFLOW_TASK_FAILED_CAUSE_RESET_WORKFLOW
Record Workflow Heartbeat	record_workflow_heartbeat	N/A

Activity

• Activity started or retried. Occurs each time an Activity is started or retried.
• Local Activity started. All Local Activities associated with one Workflow Task count as a single Action. Temporal Cloud counts all RecordMarkers from each Workflow Task as one action, and not N actions. Note:
  • Each Workflow Task Heartbeat counts as an additional Action.
  • Local Activities retried following a Workflow Task Heartbeat count as one Action (capped at 100 Actions).
• Activity Heartbeat recorded. A Heartbeat call from Activity code counts as an Action only if it reaches the Temporal Server. Temporal SDKs throttle Activity Heartbeats. The default throttle is 80% of the Heartbeat Timeout. Heartbeats don't apply to Local Activities.

Usage Name	Metric Name	History Event Type
Schedule Activity	schedule_activity	EVENT_TYPE_ACTIVITY_TASK_SCHEDULED
Retry Activity	retry_activity	EVENT_TYPE_ACTIVITY_TASK_STARTED Note: Intermediate retry attempts do not produce separate history events. Total attempt count is recorded in the ActivityTaskStartedEventAttributes.attempt field on this event. The user should subtract 1, because the first attempt is not a retry. If the Workflow is terminated while Activity retry is in progress, this STARTED event is not written, so this data may not always be available.
Retry Local Activity	retry_activity_local	EVENT_TYPE_WORKFLOW_TASK_COMPLETED Note: the retry count is recorded in WorkflowTaskCompletedEventAttributes.metering_metadata.nonfirst_local_activity_execution_attempts field on this event.
Record Activity Heartbeat	record_activity_heartbeat	N/A
Record Activity Heartbeat by ID	record_activity_heartbeat_by_id	N/A
Record Activity Markers	record_activity_markers	EVENT_TYPE_MARKER_RECORDED
Start Standalone Activity	start_standalone_activity	N/A
Retry Standalone Activity	retry_standalone_activity	N/A
Record Standalone Activity Heartbeat	record_standalone_activity_heartbeat	N/A
Record Standalone Activity Heartbeat By ID	record_standalone_activity_heartbeat_by_id	N/A

Timer

• Timer started. Includes implicit Timers that are started by a Temporal SDK when timeouts are set, such as AwaitWithTimeout in Go or condition in TypeScript.

Usage Name	Metric Name	History Event Type
Start Timer	start_timer	EVENT_TYPE_TIMER_STARTED

Signal

• Signal sent. An Action occurs for every Signal, whether sent from a Client or from a Workflow. Also, one total action occurs for any Signal-With-Start, regardless of whether the Workflow starts.

Usage Name	Metric Name	History Event Type
Signal Workflow	signal_workflow	EVENT_TYPE_WORKFLOW_EXECUTION_SIGNALED
Signal External Workflow	signal_external_workflow	EVENT_TYPE_SIGNAL_EXTERNAL_WORKFLOW_EXECUTION_INITIATED (signaler workflow history) EVENT_TYPE_WORKFLOW_EXECUTION_SIGNALED (signaled Workflow history) Note: The UI shows a billable action only in the signaled Workflow history, not in the signaler Workflow history.
Signal Workflow With Start	signal_workflow_with_start	EVENT_TYPE_WORKFLOW_EXECUTION_STARTED followed by EVENT_TYPE_WORKFLOW_EXECUTION_SIGNALED if the workflow didn’t exist, or only EVENT_TYPE_WORKFLOW_EXECUTION_SIGNALED if the Workflow existed.

Query

• Query received by Worker. An Action occurs for every Query, including viewing the call stack in the Temporal Cloud UI, which results in a Query behind the scenes. __temporal_workflow_metadata is a built-in query used to retrieve workflow metadata at runtime and is excluded.

Usage Name	Metric Name	History Event Type
Query Workflow	query_workflow	N/A

Update

• Update received by Worker.
  • Occurs for every successful Update and every rejected Update.
  • This includes Update-With-Start, and is in addition to the start Action in the case when the Workflow starts as well.
  • De-duplicated Updates that share an Update ID do not count as an Action.

Name	Action ID	History Event Type
Accept Workflow Update	accept_workflow_update	EVENT_TYPE_WORKFLOW_EXECUTION_UPDATE_ACCEPTED
Reject Workflow Update	reject_workflow_update	EVENT_TYPE_WORKFLOW_EXECUTION_UPDATE_REJECTED Note: this event is never written to history.

Schedule

Schedules allows you to schedule a Workflow to start at a particular time. Each execution of a Schedule accrues three actions:

• Schedule Start. This accounts for two actions.
• Workflow started. This is a single action to start the target Workflow. It includes initial Search Attributes as part of the start request.

Usage Name	Metric Name	History Event Type
Create Schedule	create_schedule	N/A
Update Schedule	update_schedule	N/A
Patch Schedule	patch_schedule	N/A
Delete Schedule	delete_schedule	N/A
Schedule Workflow	schedule_workflow	EVENT_TYPE_WORKFLOW_EXECUTION_STARTED Note: event.WorkflowExecutionStartedEventAttributes.indexedFields.TemporalScheduledById tells if a Workflow was started by a Schedule.

Temporal Nexus

• For Nexus Operation scheduled, the caller Workflow starting a Nexus Operation results in one Action on the caller Namespace.
• For Nexus Operation canceled, the caller Workflow canceling a Nexus Operation results in one Action on the caller Namespace.
• The underlying Temporal primitives (such as Workflows, Activities, and Signals) created by a Nexus Operation handler (directly or indirectly) result in the normal Actions for those primitives billed to the handler’s Namespace. This includes retries for underlying Temporal primitives like Activities but not for handling the Nexus Operation itself or a retry of the Nexus Operation itself.

Usage Name	Metric Name	History Event Type
Schedule Nexus Operation	schedule_nexus_operation	EVENT_TYPE_NEXUS_OPERATION_SCHEDULED
Request Nexus Operation Cancellation	request_nexus_operation_cancellation	EVENT_TYPE_NEXUS_OPERATION_CANCEL_REQUESTED

Export

Workflow History Export enables you to export closed Workflow Histories to a cloud storage sink of your choice.

• Workflow exported. Each Workflow exported accrues a single action.
• Excluded from APS calculations.

Usage Name	Metric Name	History Event Type
Export Workflow History	N/A	N/A

Fairness

For each hour a Namespace has the Fairness feature enabled, an additional 0.1 Action is charged per Action in the Namespace.

• Excluded from APS calculations.

Usage Name	Metric Name	History Event Type
Enable Fairness	N/A	N/A

Capacity

• For Namespace Capacity Temporal Resource Units (TRUs), Actions are generated up to the included hourly allocation for TRUs in any hour where TRUs are set and actual usage falls beneath the included hourly Action allocation.
• Excluded from APS calculations.

Usage Name	Metric Name	History Event Type
Enable Provisioned Capacity	N/A	N/A

Actions usage can be tracked in multiple areas depending on the needed granularity. Refer to the Billing and Usage documentation for more information.