Workflow Released

Only a single workflow with a given runId or flowControlKey can run at a time; a second one arriving before the first finishes is rejected. A single workflowRunId does not work for this because of a 10 minute deduplication window.

Workflow logs may contain sensitive data in the body or headers. Users need a way to redact these fields so they are not visible in the dashboard or API responses, preventing accidental data leaks. This also enables safer use of Workflow in multi-tenant setups where customer…

This major version of the TypeScript SDK is done with breaking changes to improve the developer experience, reduce bundle size, and simplify configuration. We have prepared a migration guide for existing users below:

An option lets a step bypass the configured retry delay and retry immediately, while retries otherwise follow the retry policy's retryAfter duration expression or default exponential backoff calculation. The change targets critical or time-sensitive operations that need rapid reprocessing of specific steps or workflow runs.

A proposed option lets a message be retried immediately, bypassing the configured retry delay. Messages otherwise retry per the configured policy, with the interval set by the Upstash-Retry-After header or an exponential-backoff default when the header is absent.

Add ability to restart or resume a workflow from the DLQ.

Workflow requires a publicly available API to send messages to. During development when applications are not yet deployed, developers typically need to expose their local API by creating a public tunnel. While local tunneling works seamlessly, it requires code changes between…

Remember last X triggers from the console so that it can be run again easily.

This is aimed for development purposes.

Add ability to list the flow-controls on the console together with their waitListSizes.

Make it searchable.

We currently provide a wait–notify mechanism that allows a workflow run to pause on an event ID and resume when a notify call is received. This works well when developers control both sides of the communication and can send the notification directly.

We currently provide JS/TS and Golang SDKs that exposes the official trigger() method to start a new workflow run. To support a broader range of use cases, we plan to introduce a REST API endpoint that allows workflows to be started via a simple HTTP call. This will enable…