openworkflowdev / openworkflowdev/openworkflow
Support manual retry for failed workflows
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 66
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 69
Description
Desired Behavior
It would be great to support manually retrying a failed workflow execution (or a failed workflow step) without restarting the entire workflow from the beginning.
In many real-world workflows, a workflow may contain multiple long-running or expensive steps. If one step fails near the end, the workflow is marked as failed and there is currently no simple way for users to manually retry it.
Ideally, OpenWorkflow could support:
manually retrying a failed workflow execution
resuming from the failed step instead of replaying all previous successful steps
retrying a specific failed step
preserving workflow history and outputs from completed steps
This would be especially useful for:
document processing pipelines
data import/export jobs
ETL workflows
multi-stage asynchronous tasks
workflows involving external APIs
Example Usage
// retry an entire failed workflow
await workflow.retry(workflowId)
// retry from the failed step
await workflow.retry(workflowId, {
fromFailedStep: true,
})
// retry a specific step
await workflow.retryStep(workflowId, "generateReport")
Example scenario:
uploadFile
→ validateFile ✅
→ parseData ✅
→ generateReport ❌
→ sendNotification
Instead of restarting the entire workflow, the user could manually retry only the generateReport step from the UI.
This would improve the user experience for long-running workflows and help avoid unnecessary recomputation and repeated external API calls.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no source files, tests, or entry points; start by locating the workflow execution and step-handling entry points. Done would require a decided design and implementation for retrying failed executions or steps while preserving completed work, history, and outputs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100