Explore October’s product updates and practical examples of building reliable applications with Temporal. If you’re considering Temporal Cloud, our new pay-as-you-go pricing has no monthly base fee.
Recently shipped#
Poller autoscaling is now Generally Available, automatically adjusting Worker poller counts as demand changes.
New Nexus features are in Pre-Release, including Nexus Invoked Standalone Activities. The release also includes Nexus SDK Ergonomics, plus Nexus IDL / Code Gen.
Moving Namespaces Across Projects is now in Pre-Release, giving teams a way to reorganize existing Namespaces as their Temporal Cloud setup changes.
Temporal Proxy is now in Pre-Release. Deploy this Temporal-published, open-source proxy in your own infrastructure. Read the documentation or explore the GitHub repository.
Builder spotlight#
How StackAI tackles document indexing failures
Document indexing failures can leave an AI application working with incomplete information. See how StackAI brought Durable Execution into its indexing pipeline to make that process more reliable.
How to Temporal#
Scope permissions for agents using Nexus
Community member Adrian Charinda Perera walks through Tenuo’s Temporal Nexus integration for agent Workflows. The approach carries task-scoped, signed permissions across service boundaries, giving teams control over specific operations and arguments.
Coordinate access to shared resources
When multiple Workflows need the same resource, your application needs to coordinate access. This Validated Pattern shows how to lock shared resources with Temporal.
Build reliable document approvals
Keep document approvals moving while people review and respond. This Validated Pattern shows how to coordinate a reliable approval process with Temporal.
Questions from the field#
Rate limits across Workflows and Workers
Gerard Palomares asked in #typescript-sdk how to keep CRM API calls within each credential’s rate limit across Workflows and Worker replicas. Aman Ullah from Xgrid discussed Task Queue Fairness and the trade-offs between dispatch throughput and accuracy at low dispatch rates.
Why history tables can keep growing after retention
Duong Le asked in #operations why history tables continued growing after closed Workflow histories should have been deleted. Temporal’s Tihomir Surdilovic explained how closed execution deletion can leave history behind for later cleanup, then updated his troubleshooting playbook in response to the discussion.
Join us live#
Headed to AWS re:Invent? Visit Booth #738 for demos, or book a meeting to explore how Temporal fits your use case. Find us at Microsoft Ignite and Web Summit, too, or join a session below.
Events
- Nov. 4–5: Open Source in Finance Forum | New York, NY
- Nov. 5: Agentic Commerce Workshop with Google and Grid Dynamics | New York
- Nov. 12: Durable AI Workflows with Temporal and MongoDB | New York, NY
- Nov. 17–19: Microsoft Ignite | San Francisco, CA
- Nov. 17: Agent builders night | Austin, TX
- Nov. 19: Building Durable Agents with Temporal + New Relic | Miami, FL
- Nov. 30–Dec. 4: AWS re:Invent | Las Vegas, NV
Webinars