How We Build It: Building Scheduled Workflows in Temporal

The text discusses how Temporal built its new Scheduler feature with an improved experience for developers. Previously, there were limitations such as schedule not being able to be stopped without affecting the running Workflow and inability to support overlapping runs. To improve upon these drawbacks, they decided to build out the new Scheduler as a Workflow. They chose this option because it allowed them to reuse existing functionality already in the server. The implementation of the scheduler directly into Temporal Server was chosen over other options like building more developer-friendly functionality on top of the existing CronSchedule implementation or building a separate scheduler system in the server. Challenges faced during this process included working with Namespaces, hiding certain Workflows from user interactions, and handling signals versus queries. The new Scheduler feature is expected to improve the developer experience for Temporal users.