microsoft / microsoft/promptflow
[Feature Request] Cache intermediate outputs for reuse if code and config stay the same
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11.2k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
We have cases where some nodes invoke very expensive DB (or other service) calls. When these nodes are embedded in a complicated flow, users don't want to rerun previously successful nodes if nothing has changed.
Describe the solution you'd like
It would be helpful if promptflow can cache intermediate outputs for reuse, but also provide an option to trigger rerun if needed.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
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 files, tests, or entry points. Start by locating promptflow's node execution and configuration-handling paths, then establish how cache keys, invalidation, and an explicit rerun option should be specified. Done should include agreed behavior and tests for reuse when code and config are unchanged and bypassing the cache when requested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ai
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100