Temporal Cloud Actions and Usage
Usage
Actions usage is tracked across an account in the usage dashboard and is visible to Account Owners, Finance Admin and Global Admin. For individual Namespaces, usage can be seen in the Namespace summary for a specific Namespace.

Actions in Workflows
When viewing a Workflow history, events that represent a Billable Action are annotated with the number consumed by the event in the Billable Actions Column. These Actions are summarized at the top of the workflow.


This Billable Action estimate is useful for projecting the cost of Workflows. For example, if you ran a test Workflow that generated 20 Billable Actions and projected that it would be run 100 times a day for a month, you could anticipate that Workflow to generate 20 Actions x 100 runs/day x 30 days = 60,000 Billable Actions per month. You can also use the Billable Action estimate to help optimize Workflows by better understanding your cost drivers.
The Billable Action estimate is an experimental feature and only measures Billable Actions that exist within Workflow event histories. Some billable concepts are not included in these calculations such as:
- Query
- Activity Heartbeats
- Rejected Update Workflow Executions
- Export
- Schedule
- Replicated Actions that occur in a Namespace replication
Additionally, Workflows with the TemporalNamespaceDivision Search Attribute set may not have accurate Billable Action
Estimates. The estimated Billable Actions should only be treated as an estimate. If billable events exist outside of
event history, the Actions count could be higher.
Reach out to our team for more information or to help size your number of Actions.