4.0.0
Concurrency limits can now take a key, so one tenant’s burst can’t starve the rest.
Feature
Add a key to any concurrency limit, like event.accountId, and runs are served in turn across keys instead of first in, first out.
The dashboard shows queue depth and wait time per key, so you can spot a noisy tenant before customers do.
Existing limits without a key behave exactly as before.
Earlier
4.2.0
Select hundreds of failed runs and replay them from the step that broke, with the fix you just deployed.
4.1.0
Human-in-the-loop requests can now be answered from Microsoft Teams and email as well as Slack.
4.0.3
Median step start latency in eu-west dropped from 180 ms to 41 ms.
Get started
Free for 50,000 steps a month. No credit card, no separate workers, and your first durable workflow deployed before lunch.