Open defunky opened 5 months ago
Based on the provided context, it seems that you are experiencing an issue where the WorkflowInput
dictionary is not persisting its values across different steps of the workflow, particularly after resuming from a bookmark. This behavior is unexpected as the WorkflowInput
should maintain its state throughout the execution of the workflow.
This could potentially be a bug in the Elsa Workflow version you are using (3.1). The expected behavior is that the WorkflowInput
should be accessible and should retain all the values that were previously set during the workflow execution, even after resuming from a bookmark.
To address this issue, you should:
WorkflowInput
.In the meantime, as a workaround, you might consider manually persisting the WorkflowInput
values across bookmarks by using a custom persistence mechanism or by storing the values in a database or cache that can be accessed after resuming the workflow.
Please let me know if you need further assistance or if there are any specific details you would like to know regarding this issue.
This comment was generated by Glime.
Description
When assigning values in the
WorkflowInput
within ActivityExecutionContext withinExecute
methods either directly via activity or via starting workflow theWorkflowInput
dictionary persists between each activity step. When an activity has a callback function via a Bookmark, accessingWorkflowInput
within this callback is empty. The expected behaviour is to maintain the Workflow Inputs throughout the lifetime of the Workflow. I believe this might be becauseWorkflowInput
can be set in theTriggerOption
class in theResumeWorkflow
and when it's not set, it will initalise an empty Dictonary instead.Steps to Reproduce
To help us identify the issue more quickly, please follow these guidelines:
Detailed Steps:
WorkflowInput
within context inside of Execute methodWorkflowInput
inside the Execute methodWorkflowInput
in the second activity containing the elements you had specifiedIWorkflowRunTime
and resume the workflow without specify any additional optionsWorkflowInput
within the callback methodWorkflowInput
is empty and the elements assign previous are lostReproduction Rate: Everytime
Expected Behavior
The
WorkflowInput
within the bookmark callback should persist all values defined previous in the current execution of the workflowActual Behavior
WorkflowInput
is empty and has no values, as a result losing all WorkflowInput values previously assignedEnvironment