microsoft/Forge

SubroutineInput - StartOverOnRetry flag

Open

#27 opened on Aug 20, 2020

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C# (59 forks)auto 404
enhancementgood first issue

Repository metrics

Stars
 (331 stars)
PR merge metrics
 (PR metrics pending)

Description

  • Current behavior is that Forge will remember the CurrentTreeNode of the Subroutine and visit that node on failover/retry.
  • What if the user would like to start from the RootTreeNode on retry?
  • I could see either behavior making sense, so we should add a property flag in SubroutineInput to determine the desired behavior.
  • Probably would need to delete all the state from subroutine session before retrying. I don't want to parse through the data though, so perhaps just starting a brand new subroutine SessionId would suffice.

Contributor guide

Research direction
Add a boolean flag 'StartOverOnRetry' to SubroutineInput. When set, on retry generate a new Subroutine SessionId to clear state and start from RootTreeNode. Update the retry logic in Forge engine to check this flag.
Tech stack
csharp
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
C#
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60