Applications often experience predictable or temporary spikes in throughput that require additional Temporal Cloud capacity. Permanently allocating peak capacity requirements for a Namespace results in unnecessary costs. However, manually adjusting capacity quotas before and after load spikes is prone to human error, risking either workflow throttling if limits are not raised in time, or runaway costs if operators forget to reduce limits after the workload subsides.
The Temporal Validated Pattern “Orchestrate temporary rate limit increases on your Namespaces” shows you how to use Temporal Workflows to orchestrate the provisioning process. A parent Workflow executes an Activity to raise the capacity limit, then starts an asynchronous Child Workflow configured with an abandon policy. The parent Workflow completes to unblock the client, while the Child Workflow waits for a designated duration before executing an Activity to revert the capacity to its original limit.