This blog post is a public copy of our monthly newsletter. If you’d like to receive upcoming updates by email, you can subscribe to our newsletter here.
Highlights from March include new product updates, hands-on tutorials, and builder spotlights from folks pushing Temporal in creative directions. You’ll also find answers to real questions from the field and a few chances to catch us live.
For more information and other things we’ve been working on, just keep reading! And as always, we’d love to hear from you. Feel free to share feedback in our Community Slack.
Recently shipped#
Lots of big launches this month. Here’s what’s new:
- Task Queue Priority and Fairness are now in Public Preview. You can now specify the order in which Tasks are dispatched on the Queue based on Priority, and you can set Fairness keys to ensure an equitable spread of compute across multiple Task types.
- Standalone Activities are now in Pre-Release! Temporal Activities can now be used on their own, outside of a Workflow as well as within one, so you can write an Activity once and use it anywhere. Get started in Go and Python.
- Our new Temporal Developer Skill guides your coding agents to write better Temporal code. It ensures your agents follow Temporal best practices and make fewer errors. We recommended the Skill for everyone using a coding agent.
- Worker Versioning is now Generally Available! This robust set of dev tools helps you avoid breaking existing Workflows during deployment. Included in this release is the Public Preview version of the Upgrade-on-Continue-as-New and Worker Controller Autoscaling capabilities.
- Namespace Endpoints are now available for all Namespaces, including those with High Availability enabled and those using API keys. It’s our recommended endpoint for the best developer experience.
Join us live#
Connect with our team to see demos from real humans. We’d love to show you exactly how we’re powering mission-critical systems at world-class organizations. That includes Replay ‘26, our annual conference, where All Time Low is headlining the afterparty. If you know, you know. If you don’t, look up “Dear Maria, Count Me In.” You’ll get it. Use code ZIGGY75 for 75% off.
EMEA/APJ:
- April 2, Spring 2026 Temporal Product Update Webinar | 4pm BST
- April 7, BankTech Asia
- April 10, Workshop Bangalore | Bangalore, IN
- April 22, AWS Summit | London
AMER
- April 2-3, MCP Dev Summit | New York, NY
- April 14, Temporal Engineering Happy Hour | San Francisco, CA
- April 22-24, Google Cloud Next | Las Vegas, NV
Builder spotlight#
This month we’ve got some new additions to the Temporal Code Exchange! This is a collection of code samples, example apps, and ideas to inspire you to build fun things with Temporal.
One of the latest projects is a Temporal MCP Server submitted by Mike Toscano, an engineering manager at Paylocity. The server connects AI assistants (or other MCP clients) and Temporal Workflow orchestration clusters.
“Rather than writing code or using the Temporal CLI manually, you can interact with your Workflows entirely through natural language, asking your AI assistant to start a Workflow, check its status, send it a Signal, cancel it, or inspect its full Event History.” Check it out!
How to Temporal#
Enabling platform engineering with Temporal: Five practical use cases
From incident response and certificate rotation to CI/CD and internal platforms, see how teams replace brittle scripts with reliable Workflows that handle retries, approvals, and long-running processes without starting over.
Questions from the field#
In the #typescript-sdk channel, community member Miquel wondered, “Can you shrink a 15 MB Workflow bundle without splitting into multiple Workers?” The Worker was consuming too much memory, much of it related to modules that weren’t even being used. Miquel discussed ideas for reducing memory usage with Roey and James from Temporal’s engineering team, ultimately deciding on a lazy loading approach. Miquel later documented the details in a blog post.
Community member Francesco Berni reported in the #operations Slack channel that his custom claim mapper wasn’t being invoked, leaving the authorizer without any valid claims. Temporal engineer David Reiss explained that the claim mapper is only called if there’s a client certificate or authorization header present. After evaluating the server configuration, Francesco found that setting the requireClientAuth parameter to true fixed the problem.