Knock Lets Teams Resume a Failed Workflow Run Where It Stopped
Knock now lets teams retry a failed workflow run from the dashboard debugger and resume where it stopped, instead of re-triggering the whole workflow.
Knock said Oct. 20 that a failed workflow run can now be retried from the workflow debugger in its dashboard. The run resumes where it left off. Teams no longer have to re-trigger the whole workflow. Knock announced the change in its product changelog.
Retries resume mid-run instead of starting over
A retried run resumes where it left off, Knock said. The only earlier fix was to trigger the workflow again. That repeated every step that had already worked. The feature is available to all Knock customers. The retry option sits in each workflow’s logs.
Knock also added content search and a Stripe listing
On Oct. 19 Knock added search across workflows, broadcasts and guides by their content, including subject lines, message bodies and template text. On Oct. 16 it said Knock is listed on Stripe’s App Marketplace. Running stripe projects add knock/project creates or links a Knock account and syncs credentials to the app’s environment, Knock said.
The take
We think resuming a run is safer than re-triggering it. A re-trigger starts the workflow over. Any step that already succeeded runs a second time. In a notification system, that can mean a customer gets the same message twice.
Resuming touches only the work that did not finish. That is the right model for a tool that messages people. We’d test it once on a staging workflow with a step that fails on purpose, then check the logs to confirm the earlier steps did not run again.
